Remove `container_repository_updated_event_id` from geo_event_log

What does this MR do and why?

According to 3-milestone column drop procedure we need 3 step process. This issue is for step 2 - "Dropping the column (release M+1)". The first step is completed in !96419 (comment 1181718552)

In the scope of this MR:

• Remove container_repository_updated_event_id column from geo_event_log table
• Remove geo_container_repository_updated_events table with all the constraints and indices

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #383747 (closed)