Wireshark 4.4.0 extcap path change breaks third party extcap installers

Summary

Follow-up on #20054 (closed) which tackled the CLI extcap args passing regression; this issue tackles the extcap binary location regression for LTS users and users upgrading to Wireshark 4.4.0+

Steps to reproduce

• either upgrade or install Wireshark 4.4.0
• install extcap, such as Edgeshark https://github.com/siemens/cshargextcap/

What is the current bug behavior?

The global (also local?) extcap plugins installed in the global location up to Wireshark 4.2.x are not found by Wireshark 4.4.0 anymore.

What is the expected correct behavior?

1. Extcap users can install or upgrade new Wireshark releases without needing to know which exact Wireshark version they use, depending on their distribution (including Windows) and without having to carefully select the matching extcap distribution package.
2. Extcap maintainers do not need to maintain:
   • complex and error-prone instructions in several places detailing which distribution package version matches which specific Wireshark version and users never reading these instructions, failing, and writing new issues.
   • complex multi-version distribution packages that multiply along distribution-package-type x Wireshark versions

If possible, support for the "legacy" extcap location for the current {Debian,Ubuntu} LTS lifetime.

Sample capture file

n/a

Relevant logs and/or screenshots

n/a

Build information

4.4.0