Change Details

Ran the migrations and confirmed this new permission works as expceted when calling `checkThreadPermission`. (Will introduce this logic in a flip the switch diff at the very end)

Tested new clients: Set the code version to current code version, created a new community and threads, confirmed that when an admin opened up the manage roles screen the manage farcaster channel tags permission was shown to the user and they could use it to create a new role. Also was logging out the value of `stateCheckStatus` and confirmed that I always got `{ status: 'state_validated' }` Tested old clients + state sync mechanism: Followed @inka's [[ https://phab.comm.dev/D12235#349120 | test plan ]] in D12235 and confirmed that the value of `stateCheckStatus` was `{ status: 'state_validated' }` {F2002608} Also confirmed that when the user opened the community drawer that the manage farcaster channel tag permission was not shown for existing communities and newly created communities

Ran the migrations and confirmed this new permission works as expceTested new clients: Set the code version to current code version, created when calling `checkTa new community and threadPermission`.s, (Will introduce this logic in a flip the switch diff at the very end)confirmed that when an admin opened up the manage roles screen the manage farcaster channel tags permission was shown to the user and they could use it to create a new role. Also was logging out the value of `stateCheckStatus` and confirmed that I always got `{ status: 'state_validated' }` Tested old clients + state sync mechanism: Followed @inka's [[ https://phab.comm.dev/D12235#349120 | test plan ]] in D12235 and confirmed that the value of `stateCheckStatus` was `{ status: 'state_validated' }` {F2002608} Also confirmed that when the user opened the community drawer that the manage farcaster channel tag permission was not shown for existing communities and newly created communities