docs(theme): embed new token documentation

[spike-rabbit]

---

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

• charts-ng
• dashboards-ng
• element-ng
• element-translate-ng
• maps-ng
• native-charts-ng

[kfenner]

@spike-rabbit I think we usually do not keep deprecated stuff in the docs? I think we should delete it and maybe link to v49 and say there you'll find the old tokens, WDYT?

Or does that confuse the AI? I thought it's maybe not great to have deprecated stuff in the docs. It's no the same as if you have a deprecated property as that is clearly marked as such but there is no such concept for SASS/CSS vars.

[spike-rabbit]

I assume/hope those were heavily used before. So I think it would be nice keeping them.
Especially since scss does not have a deprecation mechanism. So the docs might be the helpful to communicate, that those are deprecated.

[kfenner]

@panch1739 @hbxes @Killusions Do you think we should keep deprecated tokens in our documentation (marked as such in the chapter title)?

[Killusions]

@panch1739 @hbxes @Killusions Do you think we should keep deprecated tokens in our documentation (marked as such in the chapter title)?

For AI migration this would be great

[panch1739]

@spike-rabbit thank you so much for this! Regarding deprecation, i would say that we should keep it for some time so people understand that there is an architectural change here.