feat: optionally prioritize new toasts

[HenryMBaldwin]

Description

Added prioritizeNew prop to Toast.svelte to allow enabling/disabling prioritizing newer toasts when the total number of toasts exceed the maximum. Currently older toasts are prioritized, and this is still the stock behavior as the prop defaults to false.

Changsets

Instructions: Changesets automate our changelog. If you modify files in /packages, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.

Checklist

Please read and apply all contribution requirements.

• This PR targets the dev branch (NEVER master)
• Documentation reflects all relevant changes
• Branch is prefixed with: docs/, feat/, chore/, bugfix/
• Ensure Svelte and Typescript linting is current - run pnpm ci:check
• Ensure Prettier linting is current - run pnpm format
• All test cases are passing - run pnpm test
• Includes a changeset (if relevant; see above)

[changeset-bot]

🦋 Changeset detected

Latest commit: 6e97cb6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@skeletonlabs/skeleton	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
skeleton-docs	⬜️ Ignored (Inspect)	Visit Preview	May 18, 2024 4:13am

[vercel]

@HenryMBaldwin is attempting to deploy a commit to the Skeleton Labs Team on Vercel.

A member of the Team first needs to authorize it.

[endigo9740]

@HenryMBaldwin first off sorry for the long delay on this one. We've been snowed in with our pre-release prep and launches of Skeleton v3 and Floating UI Svelte.

I actually think this is a very interesting feature, and you've done a great job of following our contribution guidelines, so thanks for that. I can definitely see the appear of this feature, however, I'm cautious of adding new features this late in v2's lifecycle. As such I'm going to recommend we do the following:

1. I'm going to close out this PR without moving forward for now
2. I've already noted this concept for consideration in the pending v3 milestone issue for overlay systems
3. Then we will evaluate and find a means to implement this in a systematic manner for v3

The v3 overlay system will see us combining toasts/drawers/modals under a singular system so they can have a consistent set of features. This has a number of positive implications for users. The result will be we can add your feature once, and it'll be available for all three!

Again, I appreciate the contribution and please do look forward to a version of this feature coming in the future.

Thanks again,
Chris