Rename Cycle Analytics façades to Value Stream Analytics

What does this MR do?

We want to rename Cycle Analytics to Value Stream Analytics. This is to keep it in line with our value propositions. The first group of this work is to rename the façade aspects (UI, routes, docs etc), as per the documentation addition in !23210 (merged).

One or more future MR's will focus on the codebase aspects (BE and FE).

Note: Documentation needs reworking in some areas: #38319 (comment 275554244)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

1. Go to a project and confirm that Value Stream Analytics is found in the overview section of the menu:

2. Visit the link and confirm the page title is Value Stream Analytics and the various API calls work and show the correct data
3. Visit the analytics page:

4. Confirm the menu shows Value Stream Analytics:

5. Visit the link and confirm the page title is Value Stream Analytics and the various API calls work and show the correct data

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Closes #38319 (closed)