Add Toggle Param to Return Implied Scopes from Remix API Query Method

[allenchazhoor]

Issue

Closes https://github.com/Shopify/develop-app-runtime-primitives/issues/507

Context

Currently the query method in the Remix API does not return implied scopes but the response from Core does. This is because Remix is returning a compressed set of scopes from the response from Core, using the toArray() method in AuthScopes.

This PR adds a parameter in the AuthScopes toArray() method to toggle returning the original set of scopes returned from from the Admin API.

Type of change

• Patch: Bug (non-breaking change which fixes an issue)
• Minor: New feature (non-breaking change which adds functionality)
• Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have used pnpm changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
• I have added/updated tests for this change
• I have documented new APIs/updated the documentation for modified APIs (for public APIs)

[rezaansyed]

LGTM!

[RyanDJLee]

Thanks for taking this on - we may want to revisit our test coverage and ensure that it accurately reflects our requirements.

[RyanDJLee]

Should we consider how the other methods are implemented as well?

The current behaviour considers AuthScopes(['read_products']) equivalent to AuthScopes(['read_products', 'write_products']). Since we are encouraging developers to use this class, I wonder if this behaviour is consistent with the changes proposed in this PR / as part of the Optional scopes feature?

[RyanDJLee]

Ideally, we would want to keep the scope of this change tight and not introduce breaking changes (by changing the default behaviour). However, I wonder about the developer use cases. Would they want to compare and check inclusion with respect to the exact set of scopes or the expanded set of scopes? What about the other methods?

i.e.

required: ['read_products']
optional: ['write_products']
granted: ['read_products']

1. Developer queries for optional scopes and instantiates:

requiredScopes = AuthScope(['read_products']);
optionalScopes = AuthScope(['write_products']);
grantedScopes = AuthScope(['read_products']);

2. Developer wants to check whether the optional scopes have been granted:

grantedScopes.has(optionalScopes);
grantedScopes.equals(optionalScopes);

• Is this a realistic use case?
• Is current implementation behaving as expected in these scenarios?

cc @kbav