Skip kube-bridge interface for api/etcd address

[jnummelin]

Description

Otherwise the defaulting could pick up kube-bridge address as api/etcd address when restarting k0s if it sees it before any "real" address.

This happens on e.g. bootloose containers where kube-bridge is at index 11 and eth0 on index 18.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[k0s-bot]

Successfully created backport PR for release-1.27:

• [Backport release-1.27] Skip kube-bridge interface for api/etcd address #4472

[k0s-bot]

Successfully created backport PR for release-1.28:

• [Backport release-1.28] Skip kube-bridge interface for api/etcd address #4473

[k0s-bot]

Successfully created backport PR for release-1.29:

• [Backport release-1.29] Skip kube-bridge interface for api/etcd address #4474

[k0s-bot]

Successfully created backport PR for release-1.30:

• [Backport release-1.30] Skip kube-bridge interface for api/etcd address #4475