Fast vector tests

[BigUglySpider]

Took a diversion when inspiration hit for an approach to implementing templatised SIMD Vectors.

This adds a significant amount to EmuSIMD, but the star of the show is EmuMath::FastVector<Size_, T_, RegisterWidth_ = 128>, which provides the following benefits:

• Makes heavy use of EmuSIMD templates to provide a generic approach to interacting with SIMD Vectors of arbitrary types and widths
• Provides an interface of just a Vector, encapsulating separate registers where multiple are required and allowing the user to view it as a whole instead of multiple SIMD registers
• Easy conversions to and from EmuMath::Vector, adaptively making use of store and load intrinsics respectively when possible to optimise conversion speeds
• Adaptive behaviour dependent on multiple factors which is evaluated at compile-time
• Most EmuMath::Vector functionalities (and all that are highly common for graphical mathematics), but taking advantage of explicit use of SIMD intrinsics to boost performance
  • This includes named size variants of certain functions, which themselves may provide further optimisations
• A less generic approach to usage than EmuMath::Vector (albeit still somewhat flexible with certain functions) to prevent users from straying too far from a performance focus
• A selection of register masks to help with manipulating the Vector
• Automatic masking when results may be affected by values in registers that are not considered contained within the Vector based on its size
• Access to the underlying data (as opposed to being hidden as in EmuMath::Vector) to allow users to optimise for specific use cases
  • This is semi-risky business as the underlying data may either be an array(-like) of registers, or just a single register. This gives an inconsistent access interface when using the underlying data, but some mechanisms are provided to alleviate this (such as GetRegister).
    • There are no plans to change this as it is done to encourage some degree of (micro-)optimisation for the compiler in debug builds by omitting pointer indirections from array accesses in single-register Vectors. Additionally, the user accessing the underlying data directly is suggestive that they know what data they're working with if a generic implementation isn't good enough.

[BigUglySpider]

Note: This branch is being merged into MatrixUpdate-MiscMath as it initially branched off from it, primarily to take advantage of any new TMP items that could have been helpful. As this branch is not ready to merge into MatrixUpdate, let alone dev-unstable, this completed feature will be provided as part of the MatrixUpdate-MiscMath branch and, ultimately, placed in dev-unstable once MatrixUpdate is completed.