[http-client-java] pageable model as client response model body

[XiaofeiCao]

Describe the bug

We generate pageable models in implementation package, and we generate client response models in models package.
Issues arises when a client response model body is pageable model. Generated public client response class will have reference to implementation class.

We could do either:

1. Generate client response models in implementation package in this case
2. Don't generate client response models at all, since it's used only in pageable. There seems no sense exposing this model in this situation.

Reproduction

model QuotaLimits is Page<QuotaLimitBase> {}

list is Extension.ListByTarget<
 Extension.ScopeParameter,
 QuotaLimitBase,
 Response = ArmResponse<QuotaLimits> & {
 @header("ETag")
 eTag: string;
 }
 >;

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[weidongxu-microsoft]

Yes, I'd agree on (2), as PagedResponse already have headers within.

We may add one line in

 public static boolean responseContainsHeaderSchemas(Operation operation, JavaSettings settings) {
 if (operation.isLro() && (settings.isFluent() || settings.isDataPlaneClient())) {
 // Response headers will be omitted, as LRO method has return type as SyncPoller or PollerFlux, not
 // Response.
 return false;
 }
 return operation.hasHeaderSchemaResponse();
 }