[Bug]: current `PagingOperation` output does not support pageable decorator in nested properties

[tadelesh]

Describe the bug

for the following tsp, i got a compiler error to say list operation does not contain page items. also, the PagingOperation from getPagingOperation could not get the correct result for such nested case.

Reproduction

     @list
      op test(): ListTestResult;
      model ListTestResult {
        results: {
          @pageItems
          values: Test[];
        };
        pagination: {
          @TypeSpec.nextLink
          nextLink: string;
        };
      }
      model Test {
        id: 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.

[tadelesh]

Another two things:

1. how to deal with operation return array directly?
2. could the core export all the isXXX for paging?

[markcowl]

@tadelesh Can you include details of the error, I suspect this may be an emitter-specific error

[tadelesh]

refer this playground. current paging does not support nested @pageItems or @nextLink. it will report error and i could not get correct info from getPagingOperation.

[lmazuel]

@lirenhe @tadelesh I'm removing the E2E label, since we updated the TypeSpec to avoid this issue

[iscai-msft]

closing in favor of #2287