Add support for specifying multiple boundaries in the common test spec

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Label this issue
• Close this issue

Currently the common 'authorizing granular token permissions for GraphQL' spec block does not support specifying multiple boundary objects

We are now discovery cases where with the nested nature of GraphQL, multiple different boundaries may need to be checked/specified depending on how the user's query is constructed.

Here is an example: !243215 (merged)

As part of this ticket, we should also go fix anywhere we've let teams create alternate specs to temporarily get around the lack of multi boundary support. Here is an another case I've found: !238114 (diffs)