Updates the requirements on drupal/graphql to permit the latest version.

---
updated-dependencies:
- dependency-name: drupal/graphql
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>

The compass components are not yet importing and the output for an empty
`labels` is not an array but `null`. So we change this over to be the
same in all our compass files in the hope that they import.

The import of components from monorepos isn't working properly yet. The
Atlassian support team suggested making them manually and then adding
the generated files instead in small (~10 files) batches. This commit
contains the first ten files for which components were manually created
in compass.

The import of components from monorepos isn't working properly yet. The
Atlassian support team suggested making them manually and then adding
the generated files instead in small (~10 files) batches.

The import of components from monorepos isn't working properly yet. The
Atlassian support team suggested making them manually and then adding
the generated files instead in small (~10 files) batches.

The import of components from monorepos isn't working properly yet. The
Atlassian support team suggested making them manually and then adding
the generated files instead in small (~10 files) batches.

…ehat.yml

… the user does not start with __DELETED_USER

… address

…" module

…cs and types

…ties

…ollments

… type

…that feature is active/disabled

In the database we have table "group_relationship_field_data"
which is the data table for group content entities.
In this table, we can see the columns type, group_type and plugin_id.

The pattern for the group membership type is usually
<group_type>-<plugin>. The type (column) is limited to 32 characters,
and for example closed_challenge-group_membership (33 characters)
is just too long.

Group includes a way to generate names that fit the limits
imposed by Drupal core, and it does this consistently in its
own code. However, this means that where a <bundle>-<plugin>
concatenation would exceed the limit, it instead converts it to
'group_content_type_' . md5($preferred_id) and truncates it.
This is done in GroupRelationshipTypeStorage::getRelationshipTypeId.
The problem is that our code is naively looking at the
concatenation and doesn't handle the "too long" case, which
is handled by the group module.

To solve the problem, we replaced the type condition in the
count database query withthe plugin_id condition, because
we do not need the relationship type, which is unique per
plugin_id and group_type. Since group_type is always the
same per group entity (and we count per entity), filtering
by plugin_id instead of type gives the expected result.

In the database we have table "group_relationship_field_data"
which is the data table for group content entities.
In this table, we can see the columns type, group_type and plugin_id.

The pattern for the group membership type is usually
<group_type>-<plugin>. The type (column) is limited to 32 characters,
and for example closed_challenge-group_membership (33 characters)
is just too long.

Group includes a way to generate names that fit the limits
imposed by Drupal core, and it does this consistently in its
own code. However, this means that where a <bundle>-<plugin>
concatenation would exceed the limit, it instead converts it to
'group_content_type_' . md5($preferred_id) and truncates it.
This is done in GroupRelationshipTypeStorage::getRelationshipTypeId.
The problem is that our code is naively looking at the
concatenation and doesn't handle the "too long" case, which
is handled by the group module.

To solve the problem, we replaced the "type" condition in the
database query with the "plugin_id" condition, because
we do not need the relationship "type", which is unique per
plugin_id and group_type. Since group_type is always the
same per group entity (and we filter per entity), filtering
by "plugin_id" instead of "type" gives the expected result.

…sions

Bumps [rollup](https://github.com/rollup/rollup) from 4.14.1 to 4.22.4.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.14.1...v4.22.4)

---
updated-dependencies:
- dependency-name: rollup
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3.
- [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md)
- [Commits](micromatch/braces@3.0.2...3.0.3)

---
updated-dependencies:
- dependency-name: braces
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.2.8 to 5.2.14.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.2.14/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.2.14/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>

Updates the requirements on drupal/admin_toolbar to permit the latest version.

---
updated-dependencies:
- dependency-name: drupal/admin_toolbar
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>