Is there an existing issue for this?

• I have searched the existing issues

Expected Behavior

With a Backdrop DDEV recipe, when setting backdrop_drupal_compatibility or update_free_access in settings.php or settings.local.php (which unlike Drupal is provided by default OOTB in Backdrop), the Drupal compatibility layer should respect that setting.

Actual Behavior

Because backdrop_drupal_compatibility and update_free_access are also explicitly set in settings.ddev.php (see https://github.com/ddev/ddev/blob/master/pkg/ddevapp/drupal/backdrop/settings.ddev.php#L21), and because the DDEV settings file is loaded last, the desired settings as configured for the site never take (they are always overridden by the DDEV settings.php file). That is not expected behavior, and it should be left up to the defaults set by your Backdrop version (the backdrop_drupal_compatibility setting for instance is enabled by default in Backdrop 1.x but planned to be disabled by default in 2.x).

Steps To Reproduce

1. Install a vanilla Backdrop CMS site using the DDEV recipe.
2. Edit your settings.php file or the settings.local.php file and set $settings['backdrop_drupal_compatibility'] = FALSE;.
3. Try reading that setting via settings_get('backdrop_drupal_compatibility') (for instance using the devel module and dpm() or something) -> regardless of how that setting is configured, it is always returned as TRUE 👎🏼