Underscores aren't supported in scene names

[Exairnous]

Describe the bug
If you attempt to publish a scene with an underscore in its name it will fail to publish.

If you are using the Spoke editor, then the reported error will be: Network Error: 422 Unknown Error. Possibly a CORS error.

If you are using the Blender scene part of Spoke to create a GLB scene, then the reported error will be: Network Error: 500 Unknown Error. Possibly a CORS error.

To Reproduce
Steps to reproduce the behavior:

Spoke Editor

1. Create a new empty project.
2. Remove the Terrain_Crater1.glb from the scene.
3. Add the Ground Plane element.
4. Click on the Publish Scene button.
5. Enter test_underscores in the Project Name field and then click on the Save Project button.
6. Ensure that the Scene Name field contains test_underscores and then click on the Save and Publish button.
7. In the Performance Check dialog that appears, click on the Publish Scene button.
8. See the error dialog appear.

Note: I believe you can safely delete the project after the publish fails because a scene wasn't created that would be orphaned.

Blender scene

1. Create a new project and instead of choosing a new empty project, choose to import from Blender.
2. Click on the rectangle that says Click to select a thumbnail (16:9 .png) and choose any PNG image you have.
3. Enter test_underscores in the Scene Name field.
4. Click on the Select a scene model file (max 128mb .glb) and choose any glb file you have.
5. Click on the Publish button.
6. See the error appear beneath the Publish button.

Expected behavior
Either scene names with underscores should be rejected and the user notified that they can't be used (e.g. by field pattern matching) or underscores should be allowed and everything should work (which may require changes to Reticulum because it may not support them).

Screenshots
Spoke Editor interface warning:

Spoke Blender scene interface warning:

Desktop (please complete the following information):

• OS: GNU/Linux
• Browser: Firefox/Chromium
• Version: All versions that I've used.

Additional context
This has been a longstanding bug that looks to have been previously reported and solved, but then was re-introduced at some point and has been an infamous known (but not officially re-documented) issue ever since.

Previous related issues/commits:
#328
#329
c283a12
8825517

Possible duplicate of this issue:
#1282