Proposed changes

Since postinst failures can cause issues with packages manager (e.g. apt broken packages) which can make it harder to fix. The package status isn't dependent on the recreation of the bridge, so it shouldn't influence the install status.

The referenced ticket suggests a broader scope to improve the robustness to handle upgrade/configuration scenarios more securely, however these larger changes are not part of the scope of this PR. This PR just focuses on reducing immediate problems.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

#3408

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments