Synth-mapping-helper

This is largely a bugfix release, but I also added a table view for the warnings. Can be filtered and sorted.


* Improve performance with lots of warnings or notes, which was causing some graphs to not load. Graphs now mark just the first 100 warnings, rest can only be seen in table.
* Mark notes and rails in hand curves
* Fix velocity and acceleration plots not showing proper data, can now show X, Y and total
* Fix loading `.synth` with `null` cover image
* Decrease chunk size for `.ogg` writes in an attempt to fix errors when converting, adding silence or beat ticks
* Disable bpm calc when it fails to often to avoid affecting other functions. Can be manually retried.
* Updated dependencies
* Hide warning about `PATH` when using `install.bat`
* New [example script](https://github.com/adosikas/synth_mapping_helper/blob/main/example_scripts/rotate_existing_walls.py)
* Limit time for "already running" check to 1 second
* Fix compatiblity issue with Python 3.10/3.11 introduced in 1.4.8

Those who have used this for a long time might remember the useful plots from the [SMH companion](https://github.com/adosikas/synth_mapping_helper/wiki/Companion), which have now made it into the GUI, under the file utils tab. However, there is no auto-refresh yet, so I am not deprecating the companion just yet.
You can see X, Y as well as velocity and acceleration graphs to smooth out kinks in your rails, or fix hard jumps between patterns.

I added detection for a small number of warnings:

* Note / Rail through head area (1 square radius around head center)
* Long rail without intermediate nodes (not interpolated correctly in spiral, also boring to play)
* Position "somewhat far" from neutral position (Note 1). You can generally ignore this one, but it will look weird in spiral.
* Position "far away" from neutral position (Note 1). You can generally ignore this one, but it will look weird in spiral.

If you have ideas for more warnings, or feedback on the existing ones, let me know.
I just started with the spiral ones because I recently did some experimentation for a game bug (Note 1).


In additon to other minor bugs, I also attempted to fix the random errors when adding padding or clicks to audio, or the very least handle that better.

Note 1:
The game appears to use a odd polynomial like `output_xy=input_xy - input_xy-^5` to scale positions in spiral, which breaks down once you get more than 65 cm or ~4.75 grid squares from the "neutral position" which is the grid center for specials, and shifted left/right approximately 1.5 grid squares for left/right . If you go more than 1 meter out (~7.3 grid squares), the note even flips to the other side of the play area, because now the `input_xy-^5` term gets larger than the `input_xy-` term.

This adds "TurboStack", an extremely fast way to use the stacker. Just use the copy mode (holding CTRL) with TurboStack enabled, and it will extrapolate the movement into a stack.

Also works with symmetry, just make sure time step is large enough, or you shift the copy back a bit via Page-Up.

[!Click to see video](https://github.com/adosikas/synth_mapping_helper/assets/3721366/ce81b11c-0518-4017-bcfc-429e1504e907)

Following up the the first iteration of audio-processing from [v1.4.3](https://github.com/adosikas/synth_mapping_helper/releases/tag/v1.4.3), this release allows basic audio editing, notably:
* Convert many formats, including `.mp3` and `.flac` to `.ogg` when creating `.synth` from audio files or when replacing audio file
* Trim silence from audio
* Pad audio such that offset becomes 0
* Pad or trim audio such that first bookmark aligns with the 2-second mark (offset re-detection recommended to make beats line up again)
* Pad/trim audio by custom amount at start or end


Additional small changes in wall-art editor:
* Changing wall-type now keeps position/rotation
* Drag-behavior can once again be toggled between move/copy via a button. Holding CTRL still inverts.
* Holding shift now inverts the drag axis (time <-> x/y)
* Double-Tap of SHIFT and CTRL is now the keybind to toggle the behavior
* Suppress most browser shortcuts (this should prevent accidental CTRL-D presses trying to create bookmarks, etc)

And finally, I am continuing major code linting/cleanups in the background (which you hopefully won't notice), so that new features can be added faster.

Fixes some bugs I noticed, including the version history not displaying and changing offset shifting the data wrong.

This version completely overhauls the File-Utils tab, where you can now:

* Automatically detect BPM and Offset, with visual sections
* This should hopefully be able to replace ArrowVortex. Looking for feedback on how well it works.
* If you have a map with multiple BPM sections, just apply one first, then save, then apply the next and save to a different file.
* Several plots of intermediate data, so you can verify onsets and fine-tune bpm, including:
* Detected note onsets
* Likely beat positions
* Beat positions according to determined BPM and offset
* Error margin for offset
* Quick buttons to double/halve BPM or shift offset
* Preview audio with clicks to verify alignment
* Create `.synth` directly from `.ogg`
* No more looking for where the editor saved the initial file
* No more issues with the editor writing over files with identical names
* Replace audio file, so hopefully no more issues with the editor not properly replacing it
* Edit other metadata (including cover image)



Zoomed in on the beginning:
Above you can see that while the detected 115 BPM work ok, if I override it to 76.667 (2/3 of 115), the major onsets line up better below (offset was automatically recalculated for the override BPM).
Note that this required working in 1/3 and 1/6 throughout the map instead of 1/2 and 1/4, so YMMV.

No need to suggest the following things:

* Coverting any audio to `.ogg` (planned)
* Adding or removing silence before/after the audio (planned)
* Automatically saving multiple files based on BPM sections, for later merging (planned)
* Automatic warping (looking into it)
* I think I already extract all the required information, let me know if you got _concrete_ ideas on how to actually do it
* Automatic (timing) note generation (never going to happen)
* While incredibly useful for veteran mappers (especially for maps with "weird" tempo), I unfortunately foresee this would eventually be abused to flood the community with low-effort maps. Sorry.