Configuration folder path is fixed to config/default instead of being dynamic or configurable

[franrou]

Version 2.4.1 introduced a check to confirm the existence of the configuration folder. This check is useful for avoiding installations from configurations on sites that do not have configurations exported.

The issue is that the configuration folder is fixed to config/default, but in some projects, the configuration folder can be placed in a different location.

Solution: The config folder should be dynamic (obtaining the route from drush status) or configurable in the aljibe.yml file.

[rsanzante]

Because this issue can block some projects from using site-install the check has been removed in v2.4.2.

Let's keep this issue open to re-add it but adding a way to configure it.