Change Mapping Rules reuse to a durable function

[AndyRae]

Changes

Updates the reuse of Mapping Rules to used Durable Azure Functions. Enables reusing rules to be much quicker, and more reliable.

Includes:

• Introduces a http trigger for the rules to be reused
• Updates the CreateConcepts and MappingRules functions to be activity functions.
• Updates the Django API to call the trigger when the table ID and date event are selected, instead of queuing a job.
• The Django app is now responsible for deleting the existing rules.
• The trigger runs the orchestrator function, which:
  • Calls CreateConcepts function
  • "Fans out" to parallelise the MappingRules function, based on paginating the created concepts.
• Delete the DatabaseTest and ProcessQueue functions

The durable functions also include job statuses, which we can use in the future to monitor the status of the reuse, and make it less "eery".

I made the decision to not update the algorithm for saving rules, for time, and to persist with smaller changes.

Closes #688

Environment changes needed

Add the following environment variables to the Django app:

• [x] AZ_FUNCTIONS_URL
• [x] AZ_FUNCTIONS_RULES_NAME

Checks

Important: please complete these before merging.

• [x] Run migrations, if any.
• [x] Update changelog.md, including migration instructions if any.
• [x] Run unit tests.

[github-actions[bot]]

Tests	Skipped	Failures	Errors	Time
25	1 :zzz:	0 :x:	0 :fire:	2.682s :stopwatch: