Add support for viewing and creating objectives within an objective in a hierarchy tree

What does this MR do and why?

This MR adds ability to view children Objectives and Key Results within an Objective created under a project, it also allows for creating or adding an existing objective from the hierarchy tree view.

Limitations

The tree view currently doesn't support creating or adding Key Result, it will be added once #381833 (closed) & #385084 (closed) are addressed.

Screenshots or screen recordings

Tree View Empty State	Tree View with Objectives

Objective with Indirect Children	Objective with NO Indirect Children

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. Open rails console by running bin/rails console within GDK directory.
2. Enable the feature flag :hierarchy_db_restrictions on a project; Feature.enable(:hierarchy_db_restrictions, Project.find_by_full_path('gitlab-org/gitlab-test')).
3. Enable the feature flag :okrs_mvc on the same project; Feature.enable(:okrs_mvc, Project.find_by_full_path('gitlab-org/gitlab-test')).
4. Visit issues list page for the project by navigating to http://gdk.test:3000/gitlab-org/gitlab-test/-/issues.
5. Create an objective by clicking on dropdown button next to New issue and selecting New objective from the dropdown.
6. Once objective is created, click on it to visit its Work Item page, you should be able to see Tree View below the description.
7. Use Add dropdown button create/add objectives.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related Issues

#381872 (closed)

.gitlab/issue_templates/Navigation Proposals.md

@@ -6,8 +6,9 @@
 
 ### Checklist
 
-- [ ] If your proposal includes changes to the menu items within the left sidebar, engage the [Foundations Product Manager](https://about.gitlab.com/handbook/product/categories/#foundations-group) for approval. The Foundations DRI will work with UX partners in product design, research, and technical writing, as applicable.
+- [ ] Add relevant information to the issue description detailing your proposal, including usage and business drivers.
 - [ ] Follow the [product development workflow](https://about.gitlab.com/handbook/product-development-flow/#validation-phase-2-problem-validation) validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is strongly encouraged.
+- [ ] Engage the [Foundations Product Manager](https://about.gitlab.com/handbook/product/categories/#foundations-group) for approval. The Foundations DRI will work with UX partners in product design, research, and technical writing, as applicable.
 - [ ] Engage the [Foundations](https://about.gitlab.com/handbook/product/categories/#foundations-group) team to ensure your proposal is in alignment with holistic changes happening to the left side bar.
 - [ ] Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your nav item will live in more than one place.