Part 2 of project milestone resource refactoring

See merge request gitlab-org/gitlab!23988

Cycle unresolved threads

See merge request gitlab-org/gitlab!23123

Move jump logic into mixin.
Remove logic from consuming components.

Add more language tags

See merge request gitlab-org/gitlab!24023

Related to 32881

Fix typo in  "Milestones documentation"

See merge request gitlab-org/gitlab!23996

Add QA test for actions on prometheus alerts

See merge request gitlab-org/gitlab!23558

Redirect locked Group SSO users to SSO page instead of 500 error

See merge request gitlab-org/gitlab!20329

Remove deprecated caching class

Closes #38008

See merge request gitlab-org/gitlab!23893

Allow optional angle brackets in (Envelope-To) mail header

See merge request gitlab-org/gitlab!23797

Increase experimentation ratio for paid signup flow

See merge request gitlab-org/gitlab!23963

Update internal links to use proper suffix

Closes #198547

See merge request gitlab-org/gitlab!23647

Our style guide specifies internal links must end with a .md
suffix. This commit fixes a set of internal links that ended
with .html instead of .md.

Fix: include subgroups in security status

See merge request gitlab-org/gitlab!22653

We weren't including projects from subgroups in the security status
widget on the group security dashboard. This commit fixes that.

https://gitlab.com/gitlab-org/gitlab/issues/119021

Merge branch '119015-adjust-skip-trial-copy-in-trial-sign-up-flow-for-saas-users-who-are-logged-in' into 'master'

Adjust skip trial copy in trial sign up flow for SaaS users who are logged in

See merge request gitlab-org/gitlab!22923

Adjust skip trial copy in trial sign up flow for SaaS users who are
logged in

Update windows tags

See merge request gitlab-org/gitlab!23882

Replace pipeline custom action array header with slot and buttons

Closes #195352

See merge request gitlab-org/gitlab!22839

Closes #195352

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/22839

Move Jupyter notebooks from repository to packages

See merge request gitlab-org/gitlab!23556

Include 'license_scanning' in Usage data

See merge request gitlab-org/gitlab!23690

Add deploy_token_type column to the deploy_tokens table

See merge request gitlab-org/gitlab!23530

Added migration to add column.
Added data migration and related spec file.
Added enum for deploy_token_type in model.

Revert: Add milestone issues display limit

See merge request gitlab-org/gitlab!24004

Use NodeUpdateService in update API

Closes #199112

See merge request gitlab-org/gitlab!23894

Adds a format for relative and open date ranges

See merge request gitlab-org/gitlab!23584

This reverts merge request !23102

Upgrade to Rails 6

Closes #30030 and #31034

See merge request gitlab-org/gitlab!19891

Fix Geo Sidebar missing `active` class

Closes #199238

See merge request gitlab-org/gitlab!23885

Spec

Tests and lint

Move the clone button to the tree controls area

See merge request gitlab-org/gitlab!17752

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17752

- Improve validations of time ranges
- Use deconstructing for named parameters in functions
- Improve time range examples in jsdoc
- Switch to placing the functions in `const`

There are basically 2 big updates in this commit:

1) Split up each range type handler into a separate function
    (plus a few helper functions).
2) Export a type infer-er

The type infer-er is useful internally, but also helps me
feel more confident about code changes. In theory no 
type should ever collide with another type, so this 
function is kind of like the "canary in the coal mine" 
in that we should always be able to test a 1:1 range 
type from this function. If we can test the types 
thoroughly, we can be more confident each respective 
handler is working on the right set of data.

On that note, splitting up the logic for each range type 
makes me feel much more confident that each one is 
handled in a way that doesn't conflict with any other. 
More importantly, any potential changes to an existing 
range type or additions of new range types will: 
A) Not cause any changes to the existing ones and
B) Scale gracefully

On that final note of graceful scaling, I find the (very
common) method of basically extending a long 
if/else if/else block to be frightening from the 
perspective of ever needing to add things. I've found 
the method I use here (a dictionary lookup, in a bunch 
of cases) to be much easier to reason about: every 
addition adds a single dictionary entry, and the JS 
selects it (O(1)) when it's needed.

The date ranges can be used to represent periods of time
relative to arbitrary points in time, such as a fixed date or the
current moment.