Suppress initial interface down alarms with config option

[johannaengland]

Scope and purpose

Closes #257.

This is how I interpreted this issue: We have a config option that if it is set to true the first time a PortStateEvent would be created with the interface down state nothing happens instead.

Contributor Checklist

Every pull request should have this checklist filled out, no matter how small it is. More information about contributing to Zino can be found in the README.

• [X] Added a changelog fragment for towncrier
• [X] Added/amended tests for new/changed code
• [X] Added/changed documentation
• [X] Linted/formatted the code with black, ruff and isort, easiest by using pre-commit
• [X] The first line of the commit message continues the sentence "If applied, this commit will ...", starts with a capital letter, does not end with punctuation and is 50 characters or less long. See https://cbea.ms/git-commit/
• [ ] If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.66%. Comparing base (e2164d5) to head (1409037). Report is 9 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #367 +/- ## ======================================= Coverage 98.66% 98.66% ======================================= Files 77 77 Lines 9706 9711 +5 ======================================= + Hits 9576 9581 +5 Misses 130 130 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[johannaengland]

Settings this to draft/blocked until we get more concrete specification on how this should work