Firewall: Aliases - performance improvements when using large amounts of aliases, closes https://github.com/opnsense/core/issues/8654
missed a spot in legacy_bindings.inc, legacy_list_aliases() should be able to use the cached version of the data as well as it's only used on the frontend
Firewall: Aliases - performance improvements when using large amounts of aliases, closes https://github.com/opnsense/core/issues/8654
Cleanup model cachefiles on rc.configure_firmware and rc.configure_plugins and flush alias cache on filter reconfigure, the later ensures the aliases exist anyway at the os level.
dnsmasq: Allow multiple tags per dhcp-boot, fix tag rendering by removing - like in other parts of template (#8691)
(cherry picked from commit 24544c921c36ea8a5e9881e9e5bb44318e58db5c)
cleanup: add static $internalStaticChildren in Array fields for OPNsense/Firewall/FieldTypes to avoid accidental overlaps.
(cherry picked from commit aa66af1a143c8451ec671458f07a82f8891b057d)
Firewall: Aliases - performance improvements when using large amounts of aliases, for https://github.com/opnsense/core/issues/8654
Use cached aliases in PortField and NetworkAliasField types and refactor ModelRelationField so we can reuse recurrring patterns.
Firewall: Aliases - performance improvements when using large amounts of aliases, for https://github.com/opnsense/core/issues/8654
Skip caching when a model is bound to a legacy mapper location (in which case no version or persisted_at can exist).
Firewall: Aliases - performance improvements when using large amounts of aliases, for https://github.com/opnsense/core/issues/8654
Add a handle to flush cached data for a model, specifically in cases where a model also contains dynamic data, the responsible component for that data is also responsible for flushing its cache.
A concrete example for this is the captive portal hooking into the array class of our aliases, in which case the model data can not reliably know the state of the cache when looking at the stored data.
