Update LongVector Execution tests to now use XML

[alsepkow]

This change refactors the LongVector exec tests into their own files and swaps to use the XML and statically defined values for test input.

1. Update the LongVector exec tests to use the ShaderOpArithTable.xml TAEF table file for test entry points. This aligns with existing HLK tests.
2. Some light code cleanup.
3. Hard coded value sets in LongVectorTestData.h. Value sets give us a simple way to generate larger arrays from a smaller set of statically defined values. At a later point we can add logic to produce value sets at build time in this same header by consuming from a YAML file used in the offload test suite.
4. Move LongVector tests into their own LongVector.h, LongVector.tpp, and LongVector.cpp files.
5. Add an HLSLExecTestUtils.h file to hold some common logic to facilitate re-factoring the LongVector tests into their own files.

This PR ended up growing larger than intended. Subsequent PRs will be smaller chunks.
There are some additional refactoring and clean-up changes coming but I did not want to continue to add to this PR.

[github-actions]

✅ With the latest revision this PR passed the C/C++ code formatter.

[damyanp]

I'm guessing that the submodule changes aren't meant to be a part of this change?

[alsepkow]

I'm guessing that the submodule changes aren't meant to be a part of this change?

They are not. Accidentally grabbed those when I added the clang-format. Will fix.

[alsepkow]

Just want to note here that for subsequent PR's that add more tests cases I'm going to split these enums up by category instead of unary vs binary.
HLSLOperators, trigonometric, math, etc. And then I'll also have some child classes that inherit from LongVectorTestConfig for these various categories to help split out the logic by category and avoid large switch statements.

[bob80905]

Just some nits, take em or leave em

[tex3d]

There are some things I think we should do when taking these changes to main:

• Break up the changes into smaller parts: refactors of existing code could be reviewed and merged ahead of the code that depends on it, and make subsequent reviews much easier.
• Make sure these changes will work with the HLK content porting script (understanding changes necessary there).
• If there's a way to simplify the design to make it easier to understand, add, and maintain tests, take that into consideration.