Allow multiple instances of toast group

[peaceful-james]

Just tweaks an HTML ID and adds conditional flash rendering.
This affords using toast group in live_render.
I also snuck in some cheeky data-role attributes for easier testing and CSS hacking.

[peaceful-james]

This is the important bit.
Without being able to change this HTML ID, we get duplicate HTML IDs when we have 2 toast groups rendered, e.g. when doing live_render

[peaceful-james]

@srcrip Let me know if this PR needs anything, please.

[srcrip]

Thank you @peaceful-james! A couple thoughts:

1. I have recently worked on something in Add delay to server-error toast #19 that added some more hard dependencies on specific IDs. Not sure how exactly we'd have to reconcile or change that PR or this PR with that in mind.
2. This would have the impact on all flashes, not just the client and server error right? So the flag should probably be named as such? Maybe I'm wrong here.
3. We would really need unit tests added (I just put them in the demo folder/project) around usage in live_render
4. There was some very big changes merged recently that effect using the flash system as a proper fallback when you call put_toast immediately after a navigation. I would really like unit testing around this in particular as well, when live_render is involved

I'm not against merging this per se with some of those things addressed but I'm also curious what your use case is. Why exactly do you want to have it show up multiple times? And in your testing did this actually work properly with the state management that happens on the javascript side of the library?

[peaceful-james]

I will address these comments probably no sooner than Jan 25th. Yes, it worked in my testing. Example usage: a live_render, e.g. payment form, which can be on multiple pages, which needs its own flash/feedback/toast mechanism for messages like "payment successful!".
I will tag/ping you when it is ready for re-review.

[srcrip]

Closing for now as it appears to be stale but feel free to reopen!