Add a preference to determine how views are docked/floated

[antares1470]

Prerequisites

• Put an X between the brackets on this line if you have done all of
  the following:

  • Running the latest version of Constellation

  • Attached the Support Package via Help >
    Support Package

  • Checked the FAQs:
    https://github.com/constellation-app/constellation/wiki/FAQ

  • Checked that your issue isn’t already filed:
    https://github.com/constellation-app/constellation/issues

  • Checked that there is not already a module that provides the
    described functionality:
    https://github.com/constellation-app/constellation/wiki/Catalogue-of-Repositories

Description

Views in Constellation can be docked or floated, and these can be moved around to cater to how the user wants to arrange things in the application. By default though, each view has a spot which it gets opened into, either floating (like the Find View), or docked (like most other views) and so every time a view gets loaded (either opening the view or opening an already open view in Constellation), it gets positioned into that default spot. For users that are re-arranging where views can be found, this means they are having to make those re-arrangements every time they open Constellation.

What could be nice is the ability to customise how the view gets loaded up by default which gives users more control over their Constellation display interface. This could be done with a tab in preferences with a list of all the views available and an ability to choose for each view how they want to display it (with the default value being whatever it is currently). The view could then be loaded according to preference rather than a value preset in code.

Steps to Reproduce

1. Open Find View
2. Dock the View
3. Restart Constellation

Expected behaviour: Constellation opens any view (including find) where you want to put it

Actual behaviour: Always opens in default spot (which is floating for find)

Reproduces how often: 100%

Additional Information

Any additional information, configuration or data that might be
necessary to reproduce the issue.

[github-actions]

This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.