Update serverless concept creation to use the db

[AndyRae]

Changes

Updates the Concept Creation to use the database directly, rather than the API as previously.

This enables larger scan reports, as the previously the API would timeout and cause the process to fail.

The chain is:

• Django API triggers the RulesTrigger,
• which adds to the RulesQueue,
• which is consumed by the RulesOrchestrator,
• that "orchestrates" RulesConceptsActivity, and then RulesGenerateActivity.

The RulesTrigger initially returns a 202 with a instanceID - this can be used to check the status with WorkerStatus.

Includes:

• Convert all API methods to use the database directly
• Update typing accordingly, and fix bugs (moving from dictionaries to typed indicated some)
• Reimplement the rules queue.
• Rename functions to reflect that they are Rules related, to make it clear which part they are responsible for.
• Implement a Azure function Status, that can be used to check the status of a job.

Environment changes:

• Add rules-local queue

Closes #703 Closes #616

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:	1 :x:	0 :fire:	4.401s :stopwatch: