AzQtComponents does not attach AZ::Environment

Describe the bug
AzQtComponents does not attach to the AZ::Environment so any classes inside that use AZ memory allocators will fail. This library used to not have any components that used AZ allocators, but now does, so it should export methods to attach/detach the environment and the main programs that use AzQtComponents (AzToolsApplications, ProjectManager, etc.) should call the exported methods to attach/detach the environment.

Related issues:

• https://github.com/o3de/o3de/issues/5129
• https://github.com/o3de/o3de/issues/5128

Related branch:

• https://github.com/aws-lumberyard-dev/o3de/tree/Prism/attach-environment-azqtcomponents and commit

Steps to reproduce
Steps to reproduce the behavior:

1. Build debug binaries of the Project Manager, or other tool that uses AzQtComponents
2. Instantiate a class in AzQtComponents that uses AZ allocators (DragAndDropContextBase, ViewportDragContext, StyledTreeView) or use any EBuses that use AZ::Environment for allocators or storage in AzQtComponents.

Expected behavior
The objects can be created and used because AZ::Environment is attached providing access to the necessary allocators and env vars.

Actual behavior
AZ::Environment is not attached in the AzQtComponents dynamic library and access to allocators when using aznew will crash. Sometimes you may get lucky in profile/release builds and you will not crash because inlining will cause the allocators to use another module's environment, but this simply hides the problem.

Assets required
n/a

Screenshots/Video
n/a

Found in Branch
development

Desktop/Device (please complete the following information):

• Device: PC

Additional context
Recommend we postpone tackling this till after GA release

Start by reviewing the linked Prism branch and commit, then inspect AzQtComponents and the listed allocator-using classes: DragAndDropContextBase, ViewportDragContext, and StyledTreeView. Trace how AzToolsApplications and ProjectManager load the library. Done means AzQtComponents exposes attach/detach operations and its main consumers call them so these objects and related EBuses can use AZ::Environment safely.