Initial implementation of DatasetSpecificFilesScenarioGenerator

[craigedmunds]

Intended to allow a Redacted MRN based session to be transformed into one that can be used in a dataset.

At present, if a redacted MRN based session generator is invoked multiple times it just generates the same message repeatedly. Effectively leading to lots of updates of the same thing.

This isn't compatible with the idea of a dataset, where we expect each invocation to generate a new set of resources.

To make this work i've started to introduce a new base class DatasetSpecificFilesScenarioGenerator which will handle ensuring everything works correctly.

Intends to find the IDs of the messages, ie CHED ref, MRN, GMR and turn them into unique references, and then update other documents that reference those IDs with the correct values so that subsequent linking etc works.

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Package	Line Rate	Branch Rate	Health
TestGenerator.IntegrationTesting.Backend	76%	60%	➖
Btms.Model	91%	86%	✔
Btms.Types.Ipaffs.Mapping	77%	52%	➖
Btms.SyncJob	55%	23%	❌
Btms.Common	68%	50%	➖
Btms.BlobService	35%	23%	❌
Btms.Metrics	81%	0%	✔
Btms.Analytics	74%	74%	➖
Btms.Analytics.Export	6%	0%	❌
Btms.Business	87%	83%	✔
Btms.Backend.Data	61%	48%	➖
TestDataGenerator	86%	76%	✔
Btms.Types.Alvs.Mapping.V1.Tests	0%	0%	❌
Btms.SensitiveData	87%	95%	✔
Btms.Types.Gvms	78%	100%	➖
Btms.Azure	43%	100%	❌
Btms.Emf	11%	0%	❌
Btms.Consumers	76%	66%	➖
Btms.Types.Alvs.Mapping	80%	0%	✔
Btms.Types.Gvms.Mapping	68%	38%	➖
Btms.Types.Alvs	87%	100%	✔
Btms.Types.Ipaffs	95%	62%	✔
Btms.Backend	50%	36%	❌
Summary	78% (11023 / 14138)	65% (1108 / 1705)	➖