The current migration process for enabling/disabling blocks on landing pages has a limitation. When multiple teams work on new blocks, conflicts can arise if two migrations add new block (enable/disable) using the "availableBlocks" list. To address this,we should think about introducing a new action within the "update" mode that allows for explicit selection or deselection of blocks for the landing page. This approach would eliminate conflicts and provide more granular control over block availability during updates.