Setup automated container release process for DRANET

[gauravkghildiyal]

• [Required] When a new release tag is created, a corresponding image should be automatically pushed to registry.k8s.io/networking/dranet
• [Optional] Push a test or nightly tagged image with the latest set of changes.

[ngcxy]

I did some initial digging into the image pushing process, and it appears that automating pushes to the production registry registry.k8s.io might be challenging. According to the README for registry.k8s.io, the Image Promoter requires a manual PR to trigger the promotion of an image to production.

For our staging Docker repos, automation is enabled via k8s-staging-dranet.yaml, where images are pushed automatically every time a PR is merged.

Currently, we don't have a tag newer than v1.0.1. Moving forward, when a new tag is created, we will need to manually open a PR to promote that image from staging to prod (similar to the process in #8870).

Additionally, it would be beneficial to properly tag the latest image in the staging repo so that the most recent changes can be easily retrieved for testing purposes.