fix(css): spread lightningcss options

[bru02]

Description

Before this PR lightning.d.ts had a comment saying:

Options are spread, so you can also use options that are not typed here
like visitor (not exposed because it would impact too much the bundle size)

But, in the actual implementation the options weren't spread; so you couldn't use visitor & other non-exposed features.

Furthermore, I also exposed all LightingCSS options in the types, without impacting bundle size, by not bundling LightingCSS.

This means, if you don't havelightingcss installed, LightningCSSOptions resolves to any, but otherwise you get the full types.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[ArnaudBarre]

Oh yeah my bad I totally forgot the add the spread at the end. That's nice that TS fails very locally on the lightningCSS types reference, I need to test this on my side but like the change

[ArnaudBarre]

I've finally decided to not spread on transformStyleAttribute.
This is used very rarely and I think it will cause more bugs in the future that will solve usecases.

Thanks for this simplification of the build!

[bluwy]

Nice refactor! And thanks for spotting this improvement.