feat(proxy-hosts): group label for organising hosts

[BuenGenio]

Summary

Adds an optional group label on each proxy host so users can organise the list (e.g. by organisation, project, or any free-text label).

Changes

• Database: migration 20260402000000_host_group_label.js adds host_group_label (string, default empty) to proxy_host.
• API: OpenAPI / JSON Schema updated on proxy-host object, POST, and PUT.
• UI: Group label field on the proxy host Details tab; proxy hosts table groups rows by label with section headers; optional group filter dropdown and search includes label text.
• i18n: English strings only (en.json); other locales fall back or can be added in follow-up.

Upgrade

Migrations run automatically on backend startup (existing NPM upgrade flow).

Notes

Non-English locale files were not updated in this PR.

[nginxproxymanagerci]

Docker Image for build 2 is available on DockerHub:

nginxproxymanager/nginx-proxy-manager-dev:pr-5452

Note

Ensure you backup your NPM instance before testing this image! Especially if there are database changes.
This is a different docker image namespace than the official image.

Warning

Changes and additions to DNS Providers require verification by at least 2 members of the community!

[jc21]

Thanks for this PR — grouping proxy hosts is a frequently requested quality-of-life feature and the overall approach is solid. A few things to address before merging:

Bug — column sorting broken within groups

In Table.tsx, groups are rendered by iterating group.rows (raw data insertion order) and looking up the TanStack Row object via rowsByOriginalId. Because the visual order follows group.rows rather than tableInstance.getRowModel().rows, clicking a column header to sort has no effect on intra-group row order.

The fix is to iterate tableInstance.getRowModel().rows and insert group-header <tr> rows whenever the hostGroupLabel changes (i.e. on label transitions), rather than iterating raw groups and looking up rows by ID. That way TanStack's sort model drives the order natively.

Note: Apologies for the extra work here — table column sorting was only just merged after this PR was created, so this conflict wasn't visible at the time. Sorry for the moving target.

Minor issues

• Indentation bug in useProxyHost.ts — hostGroupLabel: "" is indented one level short compared to its siblings.
• Hardcoded English placeholder in ProxyHostModal.tsx ("e.g. Production, Development, My Project") bypasses the i18n system — should use intl.formatMessage with a key in en.json.
• No Yup validation rule for hostGroupLabel — the is-invalid CSS class check in the field template will never trigger since there is no validation rule wired up. Browser-level maxLength={150} works but doesn't give users a form-level error message consistent with the rest of the form.
• Magic string sentinel — "__all__" for "show all groups" could technically collide with a real group name. A null state or separate boolean would be safer.

Everything else looks good

• Migration is correct (NOT NULL DEFAULT '' is safe for existing rows, timestamp ordering is fine).
• host_group_label added to the required array in the response schema is correct given the DB default.
• The group filter dropdown and search-includes-label changes are clean.
• i18n strings are well structured (other locales can follow up separately as noted).

[jc21]

This conflicts with #5358 - it would be nice if you both reach a consensus on who's got the best approach. If not I will eventually have to make that call.