Refactor PATCH request of Lists so it supports the update of multiple fields

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

• Close this issue

The following discussion from !15116 (merged) should be addressed:

• @splattael started a discussion: (+1 comment)

  I am wondering what happens if the user passes max_issue_count and say position.

  Do we just update the max_issue_count and do not call super?

  Reading !15116 (diffs) it seems that previously, we also allowed updates for either collapsed or position but not both? 🤔 Is this intended?

Also this comment: !15116 (comment 218684662)

PATCH should only succeed if all fields which should be updated were updated successfully.

We might need to refactor this a bit so UpdateService and MoveService (with its lock on the list) behave nicely together in all situations.