feature: add queued status type and build step field

[shreddedbacon]

Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

To make it clear when a build or task is queued, add a queued status. This will make it so that when a build or task has been received by the remote-controller and marked as in a queue for processing, Lagoon will be able to display it as queued rather than new or pending

This also updates the enums to be the same for tasks and builds now that the remote-controller has supported using the same status types for both builds and tasks for some time.

Also adds support for buildStep to the deployment, currently Lagoon sends this data in the payload back to core, but it is not consumed by the API. This means we will be able to expose the current build step in the UI, as this build step contains useful information about which step the build is currently progressing through, or other information that could be useful at a quick glance in an overview page.

closes #3352

[shreddedbacon]

@CGoodwin90 just want to get you to 👀 the migration part to make sure it looks ok

[CGoodwin90]

Looks good to me!

[shreddedbacon]

Looks good to me!

I buggered something up, also turns out you can't do enum the way I thought, so basically now just dropping the column and recreating it seems to do the trick.

Also, I'm not 100% sure about the rollback, do I need to do the column check on rollback?

[CGoodwin90]

Looks good to me!

I buggered something up, also turns out you can't do enum the way I thought, so basically now just dropping the column and recreating it seems to do the trick.

Also, I'm not 100% sure about the rollback, do I need to do the column check on rollback?

Ah I see, turns out Knex can't alter enums after creation. An alternate approach would be to use Knex.raw - https://knexjs.org/guide/raw.html.

Don't necessarily need a column check for the rollback, but I've been adding them just incase somethng goes awry.

[shreddedbacon]

Would be good to get this in soon so that clusters with QoS enabled get some visibility of when builds are queued.

[tobybellwood]

I've reviewed the migration, and now with a safe rollback, I'm happy. I would like @rocketeerbkw to re-review the code logic

[rocketeerbkw]

Everything api/api-db wise LGTM.

One question about the actions-handler dependencies, but feel free to ignore if it doesn't make sense.