Use post compose validation:
- ensure that bridge has a valid number of entries
- use simplifiable to construct need type
- use aspect with opt to indicate allowed opts

Removes the support for specifying a job in symbol format in need.

Validates need types in Job and Bridge config.

- Only Pipeline type needs are allowed in regular jobs
- Only Bridge and Pipeline type needs are allowed in bridge jobs
- Only one Bridge type need is allowed in a bridge job

Simplified Need differentiation by adding #type to be used instead
of #bridge and #pipeline.

Moves the Needs entry to core, because it's required for use in DAG
needs.

Separates bridge and DAG needs into two separate entities to avoid any
ambiguity.

Resolve "Fix Kubernetes help text link"

Closes #34944

See merge request gitlab-org/gitlab!19121

Switch quick actions to use Zoom Meetings table and model

See merge request gitlab-org/gitlab!18620

Make `Job`, `Bridge` and `Default` to be truly inheritable

Closes #34518

See merge request gitlab-org/gitlab!18867

This changes `Job`, `Bridge` and `Default`
to use `Inheritable` to inherit the configuration.

Shared example ensure that all fields are annotated
with `inherit:` and does have matching type when inherited.

Since the `Default:` is shared, it requires that
inheritable fields to be also added to `Job` and `Bridge`.

Refactor search_tab? -> show_user_search_tab?

See merge request gitlab-org/gitlab!19205

Hide labels from issue board cards

See merge request gitlab-org/gitlab!18533

Hide role picker from profile page

See merge request gitlab-org/gitlab!19085

Include puma logs alongside rails logs in GDK

See merge request gitlab-org/gitlab!19082

Currently puma logs are emitted to a different location than rails logs.
In development environments, having a single stream of logs for puma
and rails simplifies things and ensures that developers will see puma
errors, instead of having them emitted to a file that is not usually
checked.

Resolve "Remove the `container_registry_smart_delete` feature flag."

Closes #32319

See merge request gitlab-org/gitlab!19049

Add documentation about the sync CI stage

Closes #34890

See merge request gitlab-org/gitlab!19101

Record sidekiq queuing latency

See merge request gitlab-org/gitlab!19005

Adds a Prometheus histogram, `sidekiq_jobs_queue_duration_seconds` for
recording the duration that a Sidekiq job is queued for before being
executed.

This matches the scheduling_latency_s field emitted from structured
logging for the same purpose.

Update quarantined test so that it runs (although it's still quarantined)

See merge request gitlab-org/gitlab!19203

This commit fixes comments given on a merge request

Enable the HttpOnly flag for experimentation_subject_id cookie

Closes #34851

See merge request gitlab-org/gitlab!19189

CloudFormation template for creating EKS clusters

See merge request gitlab-org/gitlab!17036

Fix `RSpec/ScatteredSetup` rubocop failure

See merge request gitlab-org/gitlab!19207

Return merge-request state in API

See merge request gitlab-org/gitlab!18888

- expose `has_conflicts` and `mergeable_discussions_state` in API
- add unit tests for the change

Merge branch '34408-reducing-the-data-being-loaded-per-design-on-first-load-of-design-management' into 'master'

[BE] Reduce the data being loaded per Design on first load

See merge request gitlab-org/gitlab!18997

- added selection by id and ids

Support query for multiple states

See merge request gitlab-org/gitlab!18518

Populate CI variables from params

Closes #24146

See merge request gitlab-org/gitlab!19023

When running a new pipeline on a
project, this commit gives the
feature of populating ci vars
from a url query string.

Workaround for QA tests when job_log_json flag is enabled

Closes #34901, #34900, and #34899

See merge request gitlab-org/gitlab!19145

This method was only ever used with the argument :members but further it
seems to have been half-implemented generically and the argument wasn't
even being used so it was just causing confusion. Since this is only
meant to be checking if the users tab should show it is now a bit more
explicit.