feat: add use:action to SidebarItem

[shinokada]

Closes #933

📑 Description

• add use:action to the a tag
• add example to docs/components/sidebar

Status

• Not Completed
• Completed

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• I have checked the page with https://validator.unl.edu/
• All the tests have passed
• My pull request is based on the latest commit (not the npm version).

ℹ Additional Information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
flowbite-svelte	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 9, 2023 7:05pm
flowbite-svelte-update	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 9, 2023 7:05pm

[shinokada]

@jjagielka Can you have a look at this PR? What do you think?

[jjagielka]

1. Your implementation of the action misses the parameters. Please take a look at Frame component where actions are implemented by 2 props: action and options.
2. Why Sidebar's a element is so special that requires the action? Why not to add it on all components?

[shinokada]

@jjagielka Thanks.
That's what I asked about your Q2. #933 (comment)

[kripi-png]

Any progress on this? I would like to have use:action available for other elements as well.
For example, on Input elements, it would allow dynamic types via a helper component.