Scope and purpose

Resolves #3482.

Replaces all uses of icons with title attributes, and a single "dropdown" tooltip, with the new .nav-tooltip tooltip component.

The "Grant privileges" tooltip in the Group Privileges form has been modified slightly:

• The tooltip trigger has been changed to include "How to guide", to signify that it is a link to an external resource.
• The tooltip trigger has been changed to be a clickable link, instead of requiring a click inside the tooltip (which is a temporary element).
• The "how to guide" anchor has been replaced with emphasis, and inclusion in the tooltip trigger text.

I have not been able to setup local JWT tokens (and as such can not visually verify the tooltip), but the change follows the standard of all other tooltips.

This pull request

• Replaces tooltips in User and API Administration tool
  • Group details
  • Token details
  • JWT details
• Replaces "Test description" tooltips in Watchdog tool

Screenshots

Before

Group permissions: Grant privileges "How to"
http://localhost:8000/useradmin/group/3/

Token details
http://localhost:8000/useradmin/tokens/detail/2/

Watchdog Test descriptions
http://localhost:8000/watchdog/

After

Group permissions: Grant privileges "How to"
http://localhost:8000/useradmin/group/3/

Token details
http://localhost:8000/useradmin/tokens/detail/2/

Watchdog Test descriptions
http://localhost:8000/watchdog/

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
• 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/
• This pull request is based 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 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