task(settings,react): Add feature flag component that supports list of oauth client ids

[dschom]

Because

• We want to feature flag certain features for certain oauth clients
• We want to be able to wrap this component around a view to feature flag it

This pull request

• Adds config oauth.reactClientIdsEnabled to flag oauth client that
• Adds oauth client feature flag component to settings, which uses the config setting above and a 'wrapper' pattern.
• Adds a general feature flag wrapper component to fxa-react.

Issue that this pull request solves

Closes: FXA-7126

Checklist

Put an x in the boxes that apply

• My commit is GPG signed.
• If applicable, I have modified or added tests which pass locally.
• I have added necessary documentation (if appropriate).
• I have verified that my changes render correctly in RTL (if appropriate).

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 099343f. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 7 targets

• nx affected --base=main --head=099343ffc4c915e2bf9c9620cf8cf5f72d0718d9 --parallel=1 -t compile
• nx run-many -t copy-gql
• nx run-many -t extract-gql
• nx affected --base=main --head=099343ffc4c915e2bf9c9620cf8cf5f72d0718d9 --parallel=3 -t lint
• nx affected --base=main --head=099343ffc4c915e2bf9c9620cf8cf5f72d0718d9 --parallel=1 -t test-unit
• nx affected --base=main --head=099343ffc4c915e2bf9c9620cf8cf5f72d0718d9 --parallel=3 -t compile
• nx run-many --parallel=1 -t build --projects=fxa-shared,fxa-auth-client,fxa-react

---

Sent with 💌 from NxCloud.

[chenba]

Approved since the code looks fine. But it's not immediately obvious where the component gets teh client id for the feature prop value?

[dschom]

it's not immediately obvious where the component gets teh client id for the feature prop value?

@chenba I guess this was left open ended on purpose, and I think it should be up to the calling code. I am under the impression that we are trying not to access hooks (or url params) directly in the components themselves. This keeps them functionally pure. It's my understanding, that resolving something like client id will be a responsibility of the page, or in the future a responsibility of the page's 'container' once that pattern is place.