Issues found in content safety modular

[qiaozha]

To summarize all issues we found in content safety DPG generation

1. Model name with Options suffix.
2. Model name for paged result is CustomPage
3. Serialized body type is incorrect.
4. Default value in outputType.

See details from this comment in the draft PR #1975

As we are targeting GA the DPG version for content safety. we need to consider some unresolved issues when we found in Modular

Tasks

Beta Give feedback

1. the api extractor not working with subpath exports. #1979
   DPG/RLC Backlog HRLC +2
2. API view should show code in different layer for modular #1980
   DPG/RLC Backlog HRLC +2
3. Split RLC from Modular #1981
   HRLC RLC +2
   

[joheredi]

Upon reviewing the main issues, I believe we should be able to resolve them within the next few weeks, aiming for a beta release by the end of September. @qiaozha, do you agree with this assessment?

Regarding the second section:

Issues #1 and #2 may require prompt attention, but they are not necessarily blocking. As a temporary solution, we could generate ApiViews for each sub-path.

For issue #3, we should definitely remove the /rest sub-path export prior to GA. We could remove the generated RLC and switch to the published RLC package post-GA as a minor update, as it wouldn't lead to any API changes. If we can achieve this before GA, great! But we should prioritize other critical issues first.

[qiaozha]

For the default value issue, because of the reasons mentioned here #1975 (comment), we decide to not set any default value for optional parameters in PR #1977

[qiaozha]

close it as have created separate issues for the rest tasks.