Scope and purpose

During testing of #3545, @johannaengland discovered that the restarting interfaces progress fails, leaving a modal that does not close. This PR fixes the bug by ensuring that all code properly awaits creation of new elements, http requests and dom updates.

In addition, this PR replaces the (why?) tooltip with a toggleable message panel (see image below). This was done as there are issues with displaying the tooltip (which as positioned fixed) within the modal element (which is also fixed). A follow-up task is to investigate whether we can support fixed tooltips in modals as well, but I opted for this solution instead of spending too much time. I also think that this is a more user-friendly solution than displaying a large tooltip within a modal element.

A message panel is shown when clicking on the (why?) element

How to test

1. Open Portadmin and find an interface you are comfortable modifying the Vlan on (e.g. one that is not linked)
2. Change the Vlan to something else, e.g. between guest and employee networks
3. Wait for the configuration and change commit to complete, then "Restarting interfaces" should be added with a progress bar.
4. Clicking "(why?)" should open the message panel.
5. When restarting interfaces completes, it should resolve with an "OK" and show a close button.

This pull request

• Fixes portadmin save functions by adding proper async/await
• Fixes bug where restart interfaces does not complete, leaving an unresolved modal
• Changes the (why?) tooltip to a message panel for functional and usability reasons

Contributor Checklist

Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to NAV can be found in the
Hacker's guide to NAV.

• Added a changelog fragment for towncrier
• Added/amended tests for new/changed code
• Added/changed documentation
• Linted/formatted the code with ruff, easiest by using pre-commit
• Wrote the commit message so that the first line 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/
• Based this pull request on the correct upstream branch: For a patch/bugfix affecting the latest stable version, it should be based on that version's branch (<major>.<minor>.x). For a new feature or other additions, it should be based on master.
• If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done
• If it's not obvious from a linked issue, described how to interact with NAV in order for a reviewer to observe the effects of this change first-hand (commands, URLs, UI interactions)
• If this results in changes in the UI: Added screenshots of the before and after
• If this adds a new Python source code file: Added the boilerplate header to that file