Run history export setup via celery, if configured

[mvdbeek]

What did you do?

• Add a history export task

This builds on #11792, which is needed so that celery workers can enqueue jobs. The workers could also do the full export, but actually creating the archive seems like it should be done by a job.

There are additional things that should be done in a MQ worker, but for that we need to be able to chain tasks, and that requires a result backend in celery (typically redis or memcached)

Why did you make this change?

(Cite Issue number OR provide rationalization of changes if no issue exists)
(If fixing a bug, please add any relevant error or traceback)

How to test the changes?

(select the most appropriate option; if the latter, provide steps for testing below)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

For UI Components

• I've included a screenshot of the changes

[mvdbeek]

And it's green! I will work on starting celery with/for tests next, but i think that's gonna be a separate piece of work and the current tests already exercise the Celery task itself.

[dannon]

This is exciting stuff. I especially really like the approach of using the same task function, simply sync, for this migration period.

[github-actions]

This PR was merged without a "kind/" label, please correct.