Scope and purpose

This PR upgrades the jQuery UI library, as part of the larger #3582 jQuery update.

How to test

Panels & Tabs

Interface Portlist

1. Search and find an IP device
2. Navigate to "Ports", and click on a port in the table
3. Verify that clicking "Activity graphs" succeeds without error in the console.

Tab Navigation plugin: Location search example

A change was made to the tab_navigation plugin to use .attr('id') instead of .selector. This plugin is used by multiple views, but it should be enough to test one such usage.

1. Find a location, e.g. "Teknobyen"
2. Verify that clicking the tabs succeeds, and that the URL is updated with the proper hash (should be #!<tabname>

You can also verify that other views with tabs work. However, they do not update the URL has value. Affected views are:

• Room search result, .e.g /search/room/100: Verify that tabs work
• IP Dev Info: Verify that tabs work.
• Syslogger: Verify that tabs work

General updates

These views have been modified to use the new jQuery UI version, but no specific changes were made to the files beyond require dependency updates.

• Dashboard: Verify that dragging and re-ordering navlets works. Tests that the $(<selector>).droppable(...) function works.
• Portadmin: No specific usage of jQuery UI that could break with the ugrade.
• Thresholds > Add: Verify that the autocomplete in the Target * input field works as expected, by searching for a target and waiting for suggestions.
• Netmap:
  • Click "View options"
  • Verify that the autocomplete in "View settings" > "Filter by room or location" works.
  • Verify that "Create new view" and "Edit view" triggers a jQuery UI dialog.
  • Verify that clicking a node in the netmap triggers a jQuery UI dialog
• Image Upload:
  • Open either a Room or Location, e.g. /search/room/100
  • Click "Edit images"
  • Make sure that there are at least two images. Upload new images if your room/location does not have enough.
  • Verify that the images can are sortable by dragging.

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