[DSDK 175] Add LedgerHQ UI library

[aussedatlo]

📝 Description

Adding the Ledger LDD Design System to the sample app, remove tailwindcss and configure styled-component.
Inspired by next.js styled component example

❓ Context

• JIRA or GitHub link: DSDK-175

✅ Checklist

Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

• npx changeset was attached.
• Covered by automatic tests.

• [ ] Impact of the changes:

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.

[vercel]

@aussedatlo is attempting to deploy a commit to the LedgerHQ Team on Vercel.

To accomplish this, @aussedatlo needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.

[jdabbech-ledger]

Shouldn't we only use naming exports ?
An eslint rule could be useful for this

[aussedatlo]

For this file, next require a default import. But I agree we should use naming exports when possible.

[valpinkman]

Why use only named exports @jdabbech-ledger ?

[aussedatlo]

Named exports are more restrictive as they require you to use a specific identifier when importing. Default exports are more flexible, you can use any name during import but may lead to inconsistencies in the codebase.

[jdabbech-ledger]

I agree with @aussedatlo on this point, moreover the IDEs follow more easily the import with naming exports in general

[alexandremgo]

Great, thank you for the added doc ;)