Partitioning: Swap base web_hook_logs table with partitioned copy

The fourth step for partitioning the web_hook_logs table (&5558 (closed)) is to swap the current non-partitioned table and the partitioned copy.

It will enable the partitioned table as the canonical web_hook_logs table to be used by the application, while the old non-partitioned table will be kept as an archive table (web_hook_logs_archived). The existing triggers will be swapped to keep the archive table in sync with the partitioned table.

The archive table will be dropped with a follow-up migration after the operation is confirmed as successful and no issues are observed.

It has to follow the successful completion of (#323675 (closed), #323676 (closed)) and will be deployed one milestone after those two are released.