fix: bundlers wrongly resolving server/client modules

[toddbaert]

Fixes an issue that can cause bundlers in repos with both the web-sdk and js-sdk to incorrectly resolve and bundle module components because both modules use the same global symbols for the API.

[toddbaert]

@moredip I'm confident enough that this is the root cause of your issue that I think we should just commit it. I've seen the same behavior myself, but it's very tough to reproduce consistently.

Regardless, there's no reason I can think of that these 2 symbols should be the same.

[codecov]

Codecov Report

Merging #445 (286ae52) into main (7e469c4) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head 286ae52 differs from pull request most recent head cfaf6c0. Consider uploading reports for the commit cfaf6c0 to get more accurate results

@@            Coverage Diff             @@
##             main     #445      +/-   ##
==========================================
- Coverage   99.47%   99.47%   -0.01%     
==========================================
  Files          25       25              
  Lines        2469     2468       -1     
  Branches      236      236              
==========================================
- Hits         2456     2455       -1     
  Misses         13       13              

Impacted Files	Coverage Δ
packages/client/src/open-feature.ts	95.60% <100.00%> (ø)
packages/server/src/open-feature.ts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[beeme1mr]

I think it make sense to use a different symbol for client and server. I'm just wondering if we should call it client and server instead of web-sdk and js-sdk. Client/server is what we went with on the main readme.

[toddbaert]

I think it make sense to use a different symbol for client and server. I'm just wondering if we should call it client and server instead of web-sdk and js-sdk. Client/server is what we went with on the main readme.

I had the same thought but went with the actual artifact name because I thought that would make it very clear in debugging. Client is a bit overloaded.