giseldo/neodataset huggingface dataset:
[Story] Add Feature splash with new releases

<!-- Title suggestion: [Story] Name of story -->

## User Story

When first logging in after a release, display a splash over the User Interface that will outline the new features and new fixes. 

## Details

Using a popup like the one seen in discord, we can easily show users things that have changed, and keep them interested in things coming up in the future

## Steps

- [ ] TBD

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

<!-- Some notes on Acceptance Criteria (AC)
If you are having issues creating Acceptance Criteria, please review [Some notes on Acceptance Criteria(AC)](https://gitlab.com/mythicteam/mythictable/-/wikis/qa/acceptace-criteria). Don't hesitate to ask for AC review or assistance in #qa, it's what we're here for.
-->

- [ ] Given: Samples Criteria exists in template
    - [ ] And: it has not been removed
    - [ ] When: the ticket has been submitted
    - [ ] Then: Someone else should update this
    - [ ] And: include acceptable Acceptance Criteria
    
<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Update Font (Space Grotesk)

# Description

Let's switch the Space Grotesk Font

## Current State

I won't think we have a consistent one.


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Improve] Documentation - Update On boarding QA to reference the new labels

# Description

The Labels have recently changed.  Make this is reflected in the Onboarding issue template.

## The Problem

- [x] ~In Progess was changed to ~"phase::active"
- [x] ~Planning was changed to ~"phase::planning" etc
- [ ] ~Bugwas changed to ~"type::bug" etc

## Solution

Go through and fix all of these in the issue template

## Steps

- [ ] TBD


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Bug] Add link back to Mythic Table from Keycloak Profile page

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "bug" label:

- https://gitlab.com/mythicteam/mythictable/issues?label_name%5B%5D=Bug

and verify the issue you're about to submit isn't a duplicate.

Title suggestion: [Bug] Brief bug description
--->

# Summary
<!--Summarize the bug encountered concisely -->
When you go to edit your profile from Mythic Table, there is no easy way to get back to where you were

## Steps to reproduce
* Open a Campaign
* Click on the Edit Profile button in the header to get to keycloak

## What is the current *bug* behavior?
* Once you are there, you cannot get back to the main page of Mythictable

## What is the expected *correct* behavior?
* Have a link, or use the cancel/save buttons to redirect you back

## Relevant logs and/or screenshots
<!--Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's tough to read otherwise. -->

## Possible fixes
<!-- If you can, link to the line of code that might be responsible for the problem -->

## Cause (Fill out after fix)
<!-- This must be filled out before the Bug can be closed.  
This is used in our post mordems to understand where we can make improvements. -->

Chose one or more:
- [ ] Work was rushed
- [ ] Plan Incomplete
- [ ] Insufficient Tests
- [ ] Missed in Review

Story points: 1.0
[Polish] Accessibility Adjustments

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description
It is worth it to go through and investigate the usability of Mythic for people with disabilities, more specifically visually impaired users, and adjust colours and design to accomodate. 

## Additional Details

Consider looking into:
- https://chrome.google.com/webstore/detail/dalton/imknobcnmlabealhbhfhpbfodgbbdnfa/related

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Bug] Chat Message Failure (class Dice.RollResult: Value class Dice.DieResult cannot be deserialized.)

# Summary

Occasionally, Chat Message fail to send. This occurs after sending a group of messages together.

## Steps to reproduce

Send any dice roll.

## What is the current *bug* behavior?

The message will be received and output. All subsequent messages will not be received. Reloading results in an error loading all message.

## What is the expected *correct* behavior?

Well, messages will be transmitted.

## Relevant logs and/or screenshots

```
Server Logs:
class Dice.RollResult: Value class Dice.DieResult cannot be deserialized.
```

```
Client Logs:
Uncaught (in promise) Error: An unexpected error occurred invoking 'SendMessage' on the server.
```

## Possible fixes

We need to take a look at deserializing the Dice.RollResult in Integration tests with the MongoDB.

## Cause (Fill out after fix)
<!-- This must be filled out before the Bug can be closed.  
This is used in our post mordems to understand where we can make improvements. -->

Chose one or more:
- [ ] Work was rushed
- [ ] Plan Incomplete
- [ ] Insufficient Tests
- [ ] Missed in Review

Story points: 3.0
[Polish] Minor artifact at bottom of scene scroll pane

# Description

Correct a tiny artifact at the bottom of the scroll pane

## Current State

![image](/uploads/2adf86909b46b27a3ec147467333a82f/image.png)


## How should it look/feel?

This is be grey like it appears when you scroll all the way down.

![image](/uploads/dbeed123390a1a0703aeacde027c9357/image.png)


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Active Scene should be more obvious

# Description

Make active scene in scene library more obvious

## Current State

![image](/uploads/99edc696a17c61b6910cc7f6c5160aeb/image.png)

## How should it look/feel?

We should experiment with a subtle border or some other effect

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Bug] Active Scene is not selected on map load

# Summary

When loading into a campaign, the active scene is not loaded.

## Steps to reproduce

Simply load into a campaign. To make it more obvious, try a campaign with more than one map such as the tutorial.

## What is the current *bug* behavior?

All scenes in the Scene library are faded/saturated.

## What is the expected *correct* behavior?

One should be more selected and appear sharper(?).

## Relevant logs and/or screenshots

Expected:

![image](/uploads/1e183b8fdea134a76847d25d4ed3fc05/image.png)

Actual:

![image](/uploads/94e024dc1b35fcb7398c2b23709c12a8/image.png)

## Cause (Fill out after fix)
<!-- This must be filled out before the Bug can be closed.  
This is used in our post mordems to understand where we can make improvements. -->

Chose one or more:
- [ ] Work was rushed
- [ ] Plan Incomplete
- [ ] Insufficient Tests
- [ ] Missed in Review

Story points: 3.0
[Improvement] Transition Character to Collection in back-end

# Description

Transitioning Characters to a Collection will impact the structure of the stored data, so it'll be best to implement this before the First Playable release: otherwise, we'll effectively have to wipe the players' campaign data and start again.

## Current State

Characters are handled separately from other collections on the back end. There's no real benefit to keeping these separate, it's just an artifact from an earlier iteration of the back end.

## How should it look/feel?

Characters should be migrated to a Collection. Back-end methods dealing with Characters specifically should be removed. Front-end methods dealing with Characters should interact with the Collection instead.

## Implementation

- On map tokens - campaign/collection/tokens
- In Library characters - user/collection/characters

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 5.0
[Polish] Add account link to "My Account" button in Campaign page

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

On the Campaign page, add a link to the account management page in Keycloak. This should probably be the currently unused "My Account" link at the top.

```
https://key.mythictable.com/auth/realms/MythicTable/account/
```

![image](/uploads/dfc4a6ccf90b1f4af477d16753987da2/image.png)

## Current State

My Account does nothing. There is no link on the campaign page to your keycloak account; this is only accessible from the tabletop.

## How should it look/feel?

No need to change the look & feel for this ticket.

Story points: 1.0
[bug] Live sessions are not restricted to campaign members

# Summary
Live sessions are not restricted to campaign members only.

## Steps to reproduce
1. Log in to URL: edge.mythictable.com
2. Select play campaign
3. Copy URL
4. Log in to separate account (not a member of the campaign)
5. Paste URL in browser
6. You will be able to see session and interact with campaign.

## What is the current *bug* behavior?
play/{CampaignId}/debug does not restrict access to campaign members

## What is the expected *correct* behavior?
play/{CampaignId}/debug path should only allow campaign members to join. If a user who is not a member attempts to join a live session, an appropriate error should be displayed.

## Cause (Fill out after fix)

Chose one or more:
- [ ] Work was rushed
- [ ] Plan Incomplete
- [ ] Insufficient Tests
- [ ] Missed in Review

Story points: 5.0
[Polish] Better tutorial maps for default campaign

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

What is the work we're doign and why?

## Current State

Plain white maps with some black text. I don't want to record it with a picture.

## How should it look/feel?

Here are some nicer tutorial maps that are styled like a dungeon:

![basic-map-interactions](/uploads/7a0a087dc7e469465aac2b2aaee063b8/basic-map-interactions.png)

![drawing-tools-chat](/uploads/73064d17a08c98cfc764953e2d6a5579/drawing-tools-chat.png)

![thank-you](/uploads/bee4ac1fb68f9d968bb26e428ebc60ee/thank-you.png)

These can replace the default maps in the tutorial campaign. Some tokens should be populated:

![basic-map-interactions_-_tokens](/uploads/83adf569ba4023c0999e77db2b2aa725/basic-map-interactions_-_tokens.png)

![drawing-tools-chat_-_Tokens](/uploads/45a6bcad373ad13c9d0d1df26c47fdf5/drawing-tools-chat_-_Tokens.png)

Story points: 2.0
[Polish] Center and in on maps on load

# Description

When you load into a map it should be centered in a way that's it's easy for the user to understand where they are.

## Current State

This is what it looks like when the campaign is loaded now:

![image](/uploads/980ea1f89726efa0e807ce5ad4a13948/image.png)


## How should it look/feel?

It might be better if it looks like this:

![image](/uploads/bbeb86c4393f1454b82bf81cbcf7da57/image.png)

Or this:

![image](/uploads/b85aaded09c2035ffcf718f70092ae9e/image.png)


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 3.0
[Polish] In-Game User Panel

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Improve design of in game user panel

## Current State

This need to be replaced to match current style:

![image](/uploads/6767164526b67aa10d82cc4f70575662/image.png)



<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Modernize Campaign Banner Upload

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Modernize Campaign Banner Upload

## Current State

The upload feature is very clunky and requires too many interactions.

![image](/uploads/12e70427b909bf721fb13951ce948578/image.png)

![image](/uploads/af9d75f1a75279072bc539818f9f44ee/image.png)

## How should it look/feel?

Just use a modern UI for this.


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Polish] Center the Campaign Creation Widget

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Center Campaign Creation Widget.

## Current State

Campaign Creation is Aligned Left. 

![image](/uploads/c30f4c7dff46709e5659bb8d6fdcca57/image.png)

## How should it look/feel?

Center this to make it look a little more modern.


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Polish] Redesign the User Panel

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Our user panel needs to match the new design and it should have a better feel.

## Current State

![image](/uploads/1bb71df125525b739e59a9aeecd91f88/image.png)

## How should it look/feel?

Modernize this.  We don't need the `Signed in as` and we can unify the look and feel.


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Remove non-core functionality from UI

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

We have a lot of dead links that suggest functionality we don't have yet.  Remove this.

## Current State

![image](/uploads/f76a99dfc0a61b563fb400fffde99559/image.png)

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Polish] Border clipping on Mythic Table Logo

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Fix teh logo so the edges aren't clipped

## Current State

![image](/uploads/bb1b1a3c80d54ec47ed1ca95adaea975/image.png)

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Polish] Consistent Style

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Have the Campaign Management Style Match the In-Game style

## Current State

This is the campaign manager:

![image](/uploads/ff9b91cef0252a9156759f4a088ff562/image.png)

This is the in game:

![image](/uploads/de5a3eaea780e792da4109825ac35dd8/image.png)

Note the style and color differences

## How should it look/feel?

Let's go with the In-game style. It is custom to Mythic Table where the campaign manager is a default style from `bootstrap`

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 3.0
[Improvement]  Use Scope on all Issue Labels that are mutually exclusive

<!-- Title suggestion: [Improvement] Name of improvement -->
<!-- Improvement Projects are interanal initiates meant to improve code quality, tests, infrastructure or process -->

# Description

Move over to using scope on all Labels

## Background/Current State

Currently we don't have a any scope on most of our labels and as a result their purpose can be confused. Furthermore 
mutliple labels of the same type can be applied to an issue confusing the state of the issue.

## Solution

Scope seems to fix this as only one label of any scope can be applied to a ticket at any given time.


<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Improvement] Auth Against Edge

<!-- Title suggestion: [Improvement] Name of improvement -->
<!-- Improvement Projects are interanal initiates meant to improve code quality, tests, infrastructure or process -->

# Description

This Improvement Project experiments with the idea of authing vs the edge env.

## Background/Current State

Currently we're using a local Mythic Auth or Keycloak instance that we're are authing against.

## The Problem

Some people struggle with the complexity that this introduces or have limitations on their local machines that prevent using a local auth solution.

## Solution

Mythic Auth supports both Edge and Local environments automatically. Or at least it has both configurations loaded. It might be simple to point a local env at the edge auth service.

<!-- A note on weights
0 is trivial. Does not involve and code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0