chore(bridge-ui): No import.meta workaround needed

[jscriptcoder]

There is no need for the previous workaround with Vite and import.meta.env vars. The problem is not that Vite isn't able to parse import.meta.env?, the problem is with import.meta?.env.

As for mocking env vars, whenever it's needed, then we could decide to route those env vars through a separate module that we can easily mock.

[codecov]

Codecov Report

Merging #13274 (4e06fa5) into main (f9f38bb) will increase coverage by 0.06%.
The diff coverage is 96.29%.

@@            Coverage Diff             @@
##             main   #13274      +/-   ##
==========================================
+ Coverage   61.55%   61.61%   +0.06%     
==========================================
  Files         119      118       -1     
  Lines        3475     3478       +3     
  Branches      485      491       +6     
==========================================
+ Hits         2139     2143       +4     
+ Misses       1251     1250       -1     
  Partials       85       85              

Flag	Coverage Δ		*Carryforward flag
bridge-ui	94.52% <96.29%> (+0.32%)	⬆️
protocol	52.37% <ø> (ø)		Carriedforward from ed0c218
relayer	64.71% <ø> (ø)		Carriedforward from ed0c218
ui	100.00% <ø> (ø)		Carriedforward from ed0c218

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files	Coverage Δ
packages/bridge-ui/src/domain/chain.ts	90.24% <96.15%> (+2.36%)	⬆️
packages/bridge-ui/src/domain/token.ts	100.00% <100.00%> (+6.25%)	⬆️

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