Remove future flag for released feature

[zzooeeyy]

WHY are these changes introduced?

Closes:

• https://github.com/Shopify/develop-app-runtime-primitives/issues/540

When optional scopes feature is released, we have the option to either:

• Enable scopes future flag by default for new apps and communicate to apps to enable this future flag to use Scopes API OR
• Remove the future flag so that apps can use Scopes API automatically.

I think removing the future flag makes more sense since we're adding new feature and not modifying existing behaviour of the library.

WHAT is this pull request doing?

Removes future flag wip_optionalScopesApi.

Top hatting

I tested by linking my app to a local version of the remix library. I can use the Scopes API without adding the future flag.

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)

[matteodepalo]

LGTM

[lizkenyon]

Just to confirm the docs for this feature is in this PR?

[zzooeeyy]

Just to confirm the docs for this feature is in this PR?

@lizkenyon -- Yes, but we don't have to merge these until we're ready to release

[kbav]

Thank you Zoey!