feat: client feature flags

[thiessenp-cds]

Summary | Résumé

Adds a React context provider to allow the client (components) to access feature flags without having to do prop drilling. There is also a slight performance improvement since the feature flags only need to pulled from Redis once per layout/page.

Testing

Test by looking using the new Repeating Sets feature.
First turn off the "Experimental Features" flag in the admin setting. Open the form builder on any form and click the "Add Form Element" button. At the bottom of the dialog there should be no option for Repeating Sets.
Second, turn on the feature, follow the same steps and now the Repeating Sets feature should show in the dialog.

[github-actions]

🧪 Review environment

https://pr4fim3gms3oiwkwmjvsvjw55e0eigqw.lambda-url.ca-central-1.on.aws/

[timarney]

We'll need to update the form filler page as well as it uses

const isAllowGrouping = await allowGrouping();

and passes to

<FormWrapper
            formRecord={formRecord}
            currentForm={currentForm}
            allowGrouping={isAllowGrouping}
          />

[thiessenp-cds]

We'll need to update the form filler page as well as it uses

const isAllowGrouping = await allowGrouping();

and passes to

<FormWrapper
            formRecord={formRecord}
            currentForm={currentForm}
            allowGrouping={isAllowGrouping}
          />

Yup, that is one of a number of pages that access that feature flag that way. There is also other feature flags. My plan was to do the forms-forms page and other pages in a followup commit. To me, this seems like less work to review and less chance to miss something in a review.
Or do you see a benefit to adding the feature flag provider AND updating all uses of client feature flags in one PR?