feat: add prefix to redis keys

[bzwei]

Monkey patch originally hardcoded redis keys used by rq and rq-scheduler to have EDA{uuid} prefix to avoid conflicts in a centralized redis env.

AAP-22834: Create named Redis key prefixes for EDA

Sample keys after the patch:

• EDAefeb4900-rq:clean_registries:activation
• EDAefeb4900-rq:results:activation-1
• EDAefeb4900-rq:worker:01fccd9976584eeab865776981ea4f9c
• EDAefeb4900-rq:clean_registries:default
• EDAefeb4900-rq:job:f91b8900-ec95-40d1-8e00-507a51fa9c9
• EDAefeb4900-rq:workers:default
• EDAefeb4900-rq:scheduler:scheduled_jobs
• EDAefeb4900-rq:job:activation-1
• EDAefeb4900-rq:workers
• EDAefeb4900-rq:finished.0
• EDAefeb4900-rq:workers:activation
• EDAefeb4900-rq:queues
• EDAefeb4900-rq:scheduler_instance:385c9b98c1304cfda83cf8dec92a0fd3

[bzwei]

@jamesmarshall24 @msmagnanijr If this PR is approved we need to make sure the scheduler in VM and OCP deployments now has a dependency on eda-api on start-up.

[bzwei]

LGTM, seems working as expected I can not see any other rq key. Automated and manual tests pass.

I strongly recommend to fully freeze the version constraint for rq stuff (rq, django-rq rq-scheduler) and take care explicitly of any library upgrade while this monkeypatch is active.

rq is now pinned to 1.13.0. django-rq is pinned to 2.8.0. rq-scheduler had been pinned to 0.10.