Feat/1246 allow reordering complex form components

[myieye]

Notable changes:

• Deleted: backend/FwLite/FwDataMiniLcmBridge.Tests/UpdateComplexFormsTests.cs, because I'm pretty sure they're out of date and have been replaced by tests that use the cleaner Api.
• I moved away from using a tuple of 3 Guids to compare ComplexEntryComponents, so that I didn't need to make BetweenPosition generic. You actually only need 1 Guid. If you're comparing complex-forms then you can use the complex-form ID. If you're comparing components then you use componentSenseId ?? componentEntryId, so you get the most specific one. For CRDTs it can be mapped back to the ComplexEntryComponent.Id before entering the API.
• I added GetDataFormat() to the MiniLcmApi in order to distinguish the two cases ☝️
• Rather than ☝️ I ended up refactoring the MiniLcmApi so that the caller needs to provide ComplexFormComponent objects, so the don't need to differentiate and the implementations have everything they need
• CanInsertComplexFormComponentViaSync proved to be a super valuable test. What cases passed and failed changed constantly as I was fleshing out the Fw implementation.

[github-actions]

C# Unit Tests

104 tests  ±0   104 ✅ ±0   5s ⏱️ ±0s
 16 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 0a031e5. ± Comparison against base commit 8dd28ee.

♻️ This comment has been updated with latest results.

[github-actions]

UI unit Tests

12 tests  ±0   12 ✅ ±0   0s ⏱️ ±0s
 4 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit a299fa5. ± Comparison against base commit bb51178.