feat: re-implement @lexical/code-shiki to let Shiki load languages on-demand

[Soxasora]

Description

Fixes #2976 by re-implementing @lexical/code-shiki allowing Shiki's default on-demand languages behavior.

This PR just demonstrates Lexical's build configuration bug, we should probably wait for a new, should be imminent, Lexical release that addresses this bug.

Screenshots

Before

After re-implementing code-shiki:

Additional Context

Was anything unclear during your work on this PR? Anything we should definitely take a closer look at?

Checklist

Are your changes backward compatible? Please answer below:

For example, a change is not backward compatible if you removed a GraphQL field or dropped a database column.

On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:

For frontend changes: Tested on mobile, light and dark mode? Please answer below:

Did you introduce any new environment variables? If so, call them out explicitly here:

Did you use AI for this? If so, how much did it assist you?

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​shikijs/​engine-javascript@​3.15.0 ⏵ 4.0.2
	@​lexical/​clipboard@​0.41.0 ⏵ 0.44.0			+1
	@​lexical/​rich-text@​0.41.0 ⏵ 0.44.0			+1
	@​lexical/​code-core@​0.44.0
	@​lexical/​selection@​0.41.0 ⏵ 0.44.0
	@​lexical/​utils@​0.41.0 ⏵ 0.44.0	+1		+1
	@​shikijs/​core@​3.15.0 ⏵ 4.0.2	+1
	@​lexical/​extension@​0.41.0 ⏵ 0.44.0	+1		+1
	shiki@​3.15.0 ⏵ 4.0.2			+1	-1
	@​lexical/​history@​0.41.0 ⏵ 0.44.0	+1		+1
	@​lexical/​html@​0.41.0 ⏵ 0.44.0			+2
	@​lexical/​headless@​0.41.0 ⏵ 0.44.0	+1		+1
	lexical@​0.41.0 ⏵ 0.44.0	-2		+1
	@​lexical/​react@​0.41.0 ⏵ 0.44.0

View full report