Introduce /api/rules/archive-by-tag endpoint

[simonbyford]

What does this change?

Does two things:

1. adds some handling to the /api/rules/csv-import endpoint to ensure the user making the request has the correct permissions. Also stores their email address against the change instead of the dummy value "CSV Import" (see: b71cd93)
2. introduces a new endpoint /api/rules/archive-by-tag which can be used to bulk-archive rules based on a given tag (see: e62afe1)

The new endpoint /api/rules/archive-by-tag accepts one parameter encoded as form-data:

• tag (required): the tag associated with the rules to archive.

For example:

curl --location 'https://manager.typerighter.gutools.co.uk/api/rules/archive-by-tag' \
--header 'accept: */*' \
--header 'content-type: application/json' \
--form 'tag="MP"'

How to test

It's slightly more complicated than the above. See these notes on the previous PR: #477 (comment)

Testing on CODE:

Kapture.2024-08-05.at.10.56.49.mp4

I'm not too sure why this particular request took 17 seconds. Subsequent requests took 200ms!

[prout-bot]

Overdue on Checker, Rule Manager (merged by @simonbyford 15 minutes and 3 seconds ago) What's gone wrong?