fix(React SSR): avoid dynamic import for the Cally calendar web component used on bq-date-picker

[dgonzalezr]

Description

The Cally calendar component that we use in the bq-date-picker component needs global registration through customElements.define(), which will cause SSR executions to fail since there's no DOM available on the server side.
The following PR refactors how to load the Cally web component via CDN instead of dynamic import, this way bundlers like Webpack or Vite won't try to handle dynamic imports during the build's static analysis phase.

On the other hand, slot changes are ignored on the server side, which is why we need to "trigger" them when the component loads (after hydration) so the changes are applied accordingly.

Related Issue

N/A

Documentation

Screenshots (if applicable)

Checklist

• I have read the CONTRIBUTING document.
• I have read the CODE OF CONDUCT document.
• I have reviewed my code.
• I have tested the changes locally.
• I have updated the documentation (if applicable).
• I have added unit tests and e2e tests (if applicable).
• I have requested reviews from relevant team members.

Additional Notes

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 1f6afb0.

Command	Status	Duration	Result
nx run beeq:storybook-build --output-style=stre...	✅ Succeeded	30s	View ↗
nx affected -t e2e --exclude=*,!tag:core --para...	✅ Succeeded	3m 54s	View ↗
nx affected -t build --exclude=*,!tag:publishab...	✅ Succeeded	2m 2s	View ↗
nx affected -t test --exclude=*,!tag:core --par...	✅ Succeeded	17s	View ↗
nx affected -t lint --exclude=*,!tag:publishabl...	✅ Succeeded	58s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-12 10:08:17 UTC

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud