When multiple MULTIGET endpoints exist, pagination model is shared

[JacobCrofts]

Medium priority, because a workaround exists.

Describe The Bug

When more than one MULTIGET endpoint exists, the _pagination object is shared between the generated Swagger models. This is a problem because:

• the pagination object's class name is tied to one of the models (for example, given Dog and Cat resources with MULTIGETs, it may be called DogMultiResponsePagination for both resources)
• the class name is subject to change when new MULTIGET endpoints are added (for example, if we add a new Parrot resource with a MULTIGET, now the class may be called ParrotMultiResponsePagination for all three resources)

This forces the developer to change the class name as new features are added. The bug is that we are defining _pagination inline in the Swagger resource, whereas it should be a separate schema.

This issue is a close relative of #176.

To Reproduce

create any two resources with MULTIGET endpoints, generate Java code, observe class name

Expected Behavior

We should have a separate "pagination" object for each resource that needs one (DogMultiResponsePagination, CatMultiResponsePagination).

Reslang Version

5.1.1

[njaczko]

Resolved by #181

[njaczko]

This issue was also discussed in slack: https://liveramp.slack.com/archives/CPBAEKS9X/p1612976567104700