[Maintenance]: Celery: TasksQueue Enum shall be refactored so that it does not contain each service name

[sanderegg]

Is there an existing issue for this?

• I have searched the existing issues

Planned changes

As found in #8233 and approved by @bisgaard-itis we agreed that:

• The TaskQueue enum purpose was to for example separate CPU and Thread bound queues, not to separate different worker application names

Proposal here is to compose the name ideally from the application name directly instead of creating yet another api-server or web-server or storage name for naming queues. Keep the constraint for CPU/Thread stuff separated.

This is a sub issue from ITISFoundation/osparc-issues#675