[flagd] use `sync_context` field instead of `GetMetadata`

[toddbaert]

[flagd] use sync_context field instead of GetMetadata

Background

Currently, to support static context enrichment via attributes sent from flagd, in-process providers call sync.GetMetadata along with starting the stream. This is not ideal. The stream isn't valid without the metadata response (since it could result in rules not functioning as expected due to missing attributes) and the metadata response is useless without the stream.

This has been implemented in flagd with this PR.
We need to absorb this change by making use of this new field in in-process providers

Requirements

• while initializing the SyncFlags stream, continue to call getMetadata, but override it with the results from the sync_context field, if present (it's optional, so its presence can be checked).
• associated tests

[leakonvalinka]

I just had a brief look at this, it seems like the GetMetadata request was never implemented for flagd in js in the first place. Since in my understanding, we want to continue to call GetMetadata for backwards compatability, it doesn't make sense to add it now I think. Should we create a new issue instead that just adds the syncContext feature to flagd?

[toddbaert]

I just had a brief look at this, it seems like the GetMetadata request was never implemented for flagd in js in the first place. Since in my understanding, we want to continue to call GetMetadata for backwards compatability, it doesn't make sense to add it now I think. Should we create a new issue instead that just adds the syncContext feature to flagd?

Absolutely! No need to implement the old thing in this case.