Allows users to switch between available organizations

This MR completely removes the frontend implementation of the sast_reports_in_inline_diff feature flag.
It includes the elimination of all conditional logic that was used to toggle between the old and new versions of inline findings.
Furthermore, this change also encompasses the removal of the frontend code related to the older inline-findings implementation.

EE: true

Remove lib/gitlab/usage_data_counters/editor_unique_counter.rb
Replace it with Internal Events for streamlined functionality

This MR completely removes the frontend implementation of the sast_reports_in_inline_diff feature flag.
It includes the elimination of all conditional logic that was used to toggle between the old and new versions of inline findings.
Furthermore, this change also encompasses the removal of the frontend code related to the older inline-findings implementation.

EE: true

It is not possible for non-admin users to create projects in private
groups, if the visibilty settings is restricted to private. The
dropdown however, did show those groups. This change will prevent
showing invalid groups

Changelog: fixed

Resolves apollo data using local resolvers

Adds unit & features specs

EE: true

Changelog: fixed

:Behind work_items_mvc_2 flag

Creates the partitioned table for ci_pipeline_variables
and attaches the table as the first partition.

Changelog: other

The single sign-on buttons have a `oauth-login-[provider]` ID in two
different contexts:

* Sign in
* Sign up

The ID is unnecessary for the sign up context, so we have decided to
remove them to avoid confusion.

Context
----------

For the group-level view of the Vulnerability Report, we exclude
archived projects.

However, the project filter list includes archived projects as
selections

We want to exclude archived projects from that list.

The list is populated by a graphql
call ([`security_dashboard/graphql/queries/group_projects.query.graphql`][1])

Which ultimately ends up calling this finder in the
[`namespace_projects_resolver`][0].

This Commit
----------

This commit adds a param to the finder to allow us to eventually filter
out archived projects in our graphql query.

As the existing behavior of this finder is to include archived
projects, the default for the new param is `include_archived: true` to
keep any other usages of this finder unaffected.

[0]:https://gitlab.com/gitlab-org/gitlab/-/blob/b1f2a2d85e2f920b1e0a98f71d1d29a9aed3fc5c/app/graphql/resolvers/namespace_projects_resolver.rb
[1]:https://gitlab.com/gitlab-org/gitlab/-/blob/b1f2a2d85e2f920b1e0a98f71d1d29a9aed3fc5c/ee/app/assets/javascripts/security_dashboard/graphql/queries/group_projects.query.graphql#L4

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/426520

- we need to associate all users with at least one organization.
- For now, we only have the default organization, so we'll use that.
  That logic could change in the future depending on changes to
  user registration logic.
- Placement as a callback and the potential drawbacks to that approach
  were considered. However, due to how users are created during
  our different types of registration, not all go through our
  creation service. It is more likely they are handled by
  a create/save operation in the `Devise::RegistrationsController`

Changelog: added

Added new setting to control enable_user_cap_member_promotion_management

Changelog: changed

Until now, copy_as_gfm feature used its own serializer to copy content
as markdown. Since content editor also has its own serializer, we remove
the serializer in use in copy_as_gfm and use the one in content editor
instead.

Changelog: changed

Changelog: changed
EE: true

This commit updates the blank sha checks around the codebase to handle
SHA256-based repositories. It also introduces a new method to determine
the blank sha based on the object format for a ceratin repository.

Changelog: changed

To avoid technical debt and improve user experience, this MR migrates
index_ml_model.vue to use graphql instead of preloading and refreshing
the page on every change to the search query and pagination.

To do so, we introduce search to the SearchableList component, in a way
that doesn't affect existent usage.

Changelog: changed

Allows to unsubscribe an individual issue email
participant from an issue using the generated
unsubscribe link in Service Desk emails.

Adds issue_email_participant_id column to
sent_notifications and FK.

Changelog: added

We are implementing graphql mutations to update and delete branch rules.
To do this we need identifiers that we can pass to the mutations. This
change uses the ProtectedBranch ID to identify Projects::BranchRule
objects and Project ID to identify Projects::AllBranchesRule and
Projects::AllProtectedBranchesRule objects.

This change also adds a `::find(id)` method to the BranchRule classes
allowing us to use global ids to find/intialize the objects.

The Global IDs will take the following formats
- `gid://gitlab/Projects::BranchRule/#{protected_branch.id}`
- `gid://gitlab/Projects::AllBranchesRule/#{project.id}`
- `gid://gitlab/Projects::AllProtectedBranchesRule/#{project.id}`

Changelog: added

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/436618

**Problem**

We allow to configure Git access protocol via UI. Implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89817. But this
functionality is not available at REST API level.

**Solution**

* Expose `enabled_git_access_protocol` value in the API response.
* Allow to provide `enabled_git_access_protocol` for POST/PUT requests.
* Verify that user has permissions to set the field
* Verify that the field is set for root group

Changelog: added

Uses alias_method to define branch_protection method
Organizes `initialize` method assignments in order of method arguments

Add cssbundling-rails and remove sassc-rails from the GitLab project.

`cssbundling-rails` enhances `assets:precompile` to invoke `yarn
build:css`. Ran the setup command for `cssbundling-rails

Added a rudimentary `build-css` script to compile assets using Dart Sass
NodeJS

because `sassc-rails` is not being used, we have to load
`sprockets/railtie` ourselves

Changelog: changed

This reverts merge request !142114

Changelog: fixed

We want to make the columns with defaults not null in our database. As
the first step, we want to validate their presence in the models.
`before_validation`s have also been added to allow existing records
to update. Otherwise, new validation would have prevented them from
getting updated.