Update Internal Tests to Use Format of (<expected>, <actual>) When Possible

[brodriguez8774]

Default Python UnitTests don't really care about ordering. It seems entirely ambiguous.

However, some custom ETC test assertions have a genuine concept of expected value and actual value which are tested together. On mismatch, then error display outputs appropriately.

Techncially these do not NEED to be in any order, but the output makes much more sense when they are.

For this reason, it's probably a good habit for internal-tests within this package to just use (<expected>, <actual>) as the default/standard way of writing tests, whenever possible. Then if any assertions need to change in the future, it will be easier and more consistent, with less work.