Investigate moving bulk work item update logic to a background on backend

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

In #557179 (closed), it was found that the work needed to bulk update certain attributes for work items often times out when a large number of items are selected. While batching these on the frontend may help as a temporary solution, ideally these operations should be done asynchronously on the backend side.

• Investigate the feasibility of moving this work to a sidekiq job
• How should the backend / frontend interact when one of the operations fails in the background? Do we need to alert the user somehow?