Update the linux-bridge component's update-policy from static to tagged.

[ashokpariya0]

What happened:
As discussed in the PR #1767, it was necessary to change the update-policy of the linux-bridge component from static to tagged once a new tag is available in containernetworking/plugins. However, it appears that the update-policy is still set to static in this file.

What you expected to happen:
Can I go ahead and raise a PR to update it to tagged as discussed? We would like to run hack/components/bump-linux-bridge.sh once PR #1927 is merged.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

[ashokpariya0]

cc @RamLavi @ormergi @oshoval

[oshoval]

sgtm, please cc Or Mergi on that PR
thanks
lets also see that all the test pass there (for that you need to inject temporary images that you build)

[oshoval]

for visibility
#1927
should be merged before updating the tag, so it will be included in the next release please

[ashokpariya0]

please check pr: #1950

[ashokpariya0]

Hi @ormergi @RamLavi
Regarding PR #1767,

We would like to move the tag to v1.5.1 and generate a new image for the latest tag.

Could you please share how you created new image with the static tag in your PR?

[ashokpariya0]

CCing @phoracek as he is the maintainer of the Linux Bridge Dockerfile: link.