Grid Abstraction - Vector Graph

[szeli1]

closes #7158
closes #4367

Grid Abstraction

This PR addresses a common pattern in lmms: grids. A grid is has regularly spaced horizontal and vertical lines forming squares where usually data is displayed. From this abstraction at least 2 widgets can benefit from: AutomationEditor and PianoRoll
GridModel:
GridModel is used to manage positions and movement on the grid. It is designed for storing below 10000 objects. For storage it uses 2 vectors, the storage structure is optimized for random access (logarithmic), adding or removing has polynomial complexity (not counting vector reallocation). GridModel can't store custom data on its own, so GridModelTyped pairs custom data to GridModel.
GridView: it draws a grid and implements selection (a functionality all grids should have).

Vector Graph

An example widget is implemented using the grid abstraction, the same widget #7158 and #4367 implements.
Comparing this vector graph to #7158:

• this graph doesn't support automation unlike New vector graph implementation #7158
• this graph doesn't support wave modulation unlike New vector graph implementation #7158
• this graph doesn't have randomized lines unlike New vector graph implementation #7158
• this graph supports selection unlike New vector graph implementation #7158
• this graph supports basic editing with keyboard shortcuts unlike New vector graph implementation #7158

Comparing this vector graph to #4367:

• this graph is placed in the original plugin, unlike Improved Waveshaper / Spline-based graph replacement #4367
• this graph doesn't have as many line types unlike Improved Waveshaper / Spline-based graph replacement #4367
• this graph supports selection unlike Improved Waveshaper / Spline-based graph replacement #4367
• this graph supports basic editing with keyboard shortcuts unlike Improved Waveshaper / Spline-based graph replacement #4367
• this graph can be saved unlike Improved Waveshaper / Spline-based graph replacement #4367

How to test:

1. open lmms
2. add the waveshaper effect to an instrument
3. the new VectorGraph should be there
4. place points with LMB
5. remove points with RMB
6. hold ctrl and LMB to select
7. use keyboard shortcuts Key_Up, Key_Down, Key_Right, Key_Left to move selection with the keyboard.
8. use keyboard shortcuts shift + Key_Up, Key_Down, Key_Right, Key_Left to select.
9. use keyboard shortcuts ctrl + Key_Up, Key_Down, Key_Right, Key_Left to move selected points.
10. use keyboard shortcuts ctrl + Key_C, Key_V, Key_X, Key_A to copy, paste, cut and select all
11. use keyboard shortcut Key_Delete to delete
12. use keyboard shortcut ctrl + Key_T (or mouse wheel) to change the line type of the selected points. The line types are "bezier", "attribute", "sine", "peak" and "steps".
13. "attribute" type points are displayed smaller. Use these points to configure all other line types. "attribute" points should have not "attribute" points before and after.
14. test saving and loading

[Veratil]

From what I can find it looks like we can do something like this instead of creating our own type here:

#if defined(_MSC_VER)
#include <BaseTsd.h>
using ssize_t = SSIZE_T;
#endif

You can see all the types defined in this header here: https://learn.microsoft.com/en-us/windows/win32/winprog/windows-data-types

[szeli1]

I think it is fine to use signed long long in the code. Maybe I will remove this line and replace every 2 references of signedSize with long long.

[messmerd]

We shouldn't include a Win32 header.

I'd recommend using either std::int64_t or this:

using ssize_t = std::make_signed_t<std::size_t>;

[messmerd]

The view shouldn't own the model. A non-owning pointer to the model should be passed to the view in the view's constructor.