Action buttons don't result in data reloads (tasks, deployments, etc..)

[shreddedbacon]

The UI doesn't always update or refresh properly when clicking buttons like "add task" or "new deployment" and this can lead to users clicking buttons twice because the first time didn't see a positive reaction.

The result of clicking buttons twice can result in multiple tasks or deployments being triggered.

I'm not sure if this is related to subscriptions in the API/UI getting exhausted (uselagoon/lagoon#1344). Could we just have the button actions in the UI force reload pages instead?

Additonally, if there is an error returned, exposing the error in a nice way so users don't have to dig through network tabs or console logs.

[tnelson-doghouse]

My thoughts: When the button is clicked, display a "loading" thing (with everything greyed out) before the actual update happens, so that people don't click twice; they still have to reload, but it's a lot more obvious what's going on.