feat: add proposal for ofo flagd client support

[skyerus]

This PR

OFEP for ofo flagd client support

Related Issues

• https://github.com/open-feature/open-feature-operator/issues/371

Notes

• Summary of the PoC: https://github.com/open-feature/open-feature-operator/issues/371#issuecomment-1468511819

Follow-up Tasks

• Discuss during at an office hours session

[skyerus]

As a result of our office hours discussion, a decision has been made to defer this extension of OFO to support deployment patterns, in lieu of documentation and templating for typical deployment patterns.

Main reasoning against using OFO to manage the deployment:

• There's a huge variety of unknown deployment patterns by potential users. Catering to one likely means scope creep to support many in future. Perhaps this is the future path of this project but we agreed it is best to keep things simple and minimally scoped at this stage (until common deployment patterns are more established).
• OFO would require CRUD permissions for HTTPRoutes & Gateways, introducing security concerns.
• Kubernetes Gateway API is still in beta.

Next steps:

• [x] Update the OFEP to defer (potentially forever) the extension
• [ ] Replicate the POC via templating

[skyerus]

All I did is remove the approval from James, not sure why GH took it upon itself to remove the request for review from others 🤦