Prioritize queueing of Dagster assets and pipelines

[blarghmatey]

Description/Context

The current configuration of the Dagster instance is using the QueuedRunCoordinator with a maximum concurrent steps of 10. We can customize this to either just increase/decrease that maximum concurrency, or we can set priority ordering of different tasks to prevent more urgent tasks from getting blocked by lower priority/slower steps.

Plan/Design

• Determine the relative priorities of the different asset groupings and what type of groupings we want to have for the priority queues (e.g. based on resource constraints such as Airbyte or Open edX, or by task speed/frequency, etc.)
• Update the Dagster configuration here with the proper configuration based on documentation found here
• Apply any asset/operation tagging that is necessary to support the queue priorities and concurrency limits.