Move non-deps and shared UI code in shared folder

[tytan652]

Description

• Move non-deps module from the deps folder to the shared folder
• Move UI code that was used in various frontend-plugins as module in the shared folder

Find Qt with versionless removed to avoid this issue on Ubuntu CI: (fixed)

Motivation and Context

Based on ideas from this #9220 (comment)

I would also suggest not adding new things to the "deps" directory - its purpose was for vendors external dependencies, but this PR extends its use for "shared modules". I'd much rather have us use a new directory called "shared", "common", or some other that communicates this purpose.

The solution to this would be to move UI elements shared by modules/plugins to be moved into the same "shared" directory and be made a standalone library

That would also fix this outstanding issue with the frontend plugins which "magically" pull in sources from the UI source tree that they shouldn't actually know about

How Has This Been Tested?

• Builds
• PropertiesView are translated correctly.

Types of changes

• Tweak (non-breaking change to improve existing functionality)

• Code cleanup (non-breaking change which makes code smaller or more readable)

Checklist:

• My code has been run through clang-format.
• I have read the contributing document.
• My code is not on the master branch.
• The code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation.

[tytan652]

I will push commit by commit to check if each commit (except the a few) builds on Windows and macOS.

[tt2468]

I think common would be a better name for these specific cases. Otherwise, I like this

[tytan652]

I think common would be a better name for these specific cases.

There is this thread #9350 (comment) in the PR, about the name. It was resolved, so I guess it was indeed discussed.

If the name should be (re-)discussed, I would prefer it being done off-thread with a clear consensus on one name.

[PatTheMav]

I think common would be a better name for these specific cases.

There is this thread #9350 (comment) in the PR, about the name. It was resolved, so I guess it was indeed discussed.

If the name should be (re-)discussed, I would prefer it being done off-thread with a clear consensus on one name.

The result of the discussion boiled down to "we're not entirely happy with 'shared' but also haven't come up with a compelling alternative". Also given that it should be trivial to change this later, we didn't necessarily wanted to block the PR over it.