Add v2 approval rule associations to protected branches for new approval rule architecture

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

• Work on this issue
• Close this issue

Add new v2 approval rule associations to protected branches for new approval rule architecture. Update the associations for v2 approval rules accordingly.

Both tables will need to have a defined sharding key similar to !179861 (merged).

For reference consult the new architecture in the Architecture Design Document and the tables which were created in Draft: [ci skip][DO NOT MERGE][PoC] Start of Po... (!171114 - closed) and Draft: [ci skip][DO NOT MERGE][PoC] Integrate v... (!174517).