CHI-2818 queue transfer capacity workaround

[stephenhand]

Description

Adds explicit chat capacity reductions for worker with original task after a transfer. THis prevents a race condition where they can be assigned a new task before their chat capacity is decreased due to completing the task

Also adds an 'increaseUntilCapacityAvailable' mode for adjustChatCapactity that will keep increasing chat capacity until capacity becomes available or the max capacity is reached. I was concerened that 'double decreases' could leave a worker with too low a capacity to pull tasks in some scenarios so this works around that

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags / configuration added

Other Related Issues

None

Verification steps

See ticket - ensure worker and queue transfer scenarios are working

Also, ensure that if a worker picks up 3 tasks, then transfers 1 away, they can still pull yet another from the queue.

AFTER YOU MERGE

1. Cut a release tag using the GitHub workflow. Wait for it to complete and the notification to be posted in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[murilovmachado]

Looks good to me