Remove Group CI minutes usage old app

What does this MR do and why?

Issue: #360784 (closed)

This is part of a list of MRs that clean up the old code for the Pipelines Tab in the Usage Quotas page. This removes the old frontend files for Group Usage Quotas.

PoC !104710 (closed)

Title	MR	Description
Remove usage_quotas_pipelines_vue feature flag	!105487 (merged)	With this MR all the old JS/ruby code will never be executed because it's never being included. This gives us more piece to break down the JS removals in more MRs. We can remove the FF as well, at this point
Remove remaining old ruby code for usage quotas - pipelines	!105723 (merged)	This finishes the removal of all dead code on the backend
Remove Group CI minutes usage old app	!105795 (merged)	You're here
Remove Profile CI minutes usage old app	!105880 (merged)	Removes the old frontend files for Profile Usage Quotas. This finishes the removal of all dead code on the frontend

Screenshots or screen recordings

No UI changes. Details: #360785 (comment 1180904501)

How to set up and validate locally

1. Checkout the branch
2. Visit: http://gdk.test:3000/groups/flightjs/-/usage_quotas#pipelines-quota-tab
3. Visit: http://gdk.test:3000/-/profile/usage_quotas#pipelines-quota-tab
4. Make sure both pages are rendering correctly

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.

.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.