Using ddev-drupal-contrib with label_help

Problem/Motivation

When spinning up a local environment for development of the Label Help module, we now see a warning upon ddev start due to changes in how Gitlab Templates does symlinking, and therefore presumably also how ddev symlink-project works.

• Issue: #3497525: Only symlink to the project's own files
• Change Record: #3500320 symlink_project.php uses environment variable PROJECT_FILES

WARNING: The list of project files and folders has been derived here, because the environment variable PROJECT_FILES is empty.
Array
(
    [2] => .ddev
    [3] => .editorconfig
    [5] => .gitattributes
    [6] => .gitignore
    [7] => .gitlab-ci.yml
    [8] => .prettierignore
    [9] => .prettierrc.json
    [10] => .vscode
    [11] => LICENSE.txt
    [12] => README.md
    [13] => composer.json
    [14] => composer.lock
    [15] => config
    [16] => css
    [17] => label_help.info.yml
    [18] => label_help.libraries.yml
    [19] => label_help.module
    [20] => modules
    [21] => node_modules
    [22] => phpcs.xml.dist
    [23] => phpstan-baseline.neon
    [24] => phpstan.neon
    [25] => recipes
    [26] => templates
    [27] => tests
)

This may not be accurate and to avoid this warning, at the start of your customized composer script execute the following command:

export PROJECT_FILES=$(ls -A)

See change record https://www.drupal.org/node/3500320 for more details
************************************************************************************************************************

Creating symlinks in /var/www/html/web/modules/custom/label_help pointing back to files in /var/www/html
.ddev
.editorconfig
.gitattributes
.gitignore
.gitlab-ci.yml
.prettierignore
.prettierrc.json
.vscode
LICENSE.txt
README.md
composer.json
composer.lock
config
css
label_help.info.yml
label_help.libraries.yml
label_help.module
modules
node_modules
phpcs.xml.dist
phpstan-baseline.neon
phpstan.neon
recipes
templates
tests

Proposed resolution

Update ddev and ddev-drupal-contrib scripts to latest version, in hopes that this remedies the warning.

Remaining tasks

User interface changes

API changes

Data model changes