feat: Allow installing and testing with all database types, including MariaDB

[rfay]

(Draft: This has to be rebased after

• fix: Install drush without affecting git index #33
• Final config for use with DDEV v1.23.1, replaces #30, replaces #23 #31

This PR allows using any database type supported by DDEV, including MariaDB and MySQL. And of course it can still use sqlite.

It currently includes unmerged PRs because drush is required for it.

I guess it still needs tests, will wait until after rebase.

[joachim-n]

@rfay Could you rebase this against main please? There are a lot of conflicts and I don't know what I'm doing with the code involved.

[rfay]

I can rebase this and #33, but it will still be dependent on #33

[joachim-n]

Ah drat, I hadn't seen this depended on #33. Too many balls in the air, sorry!

[joachim-n]

I don't know if in my fork I want to support both styles of installation, or just using my Composer project template. I was initially thinking I'd support both, if it's not too much faff.

[rfay]

This is rebased against

• fix: Install drush without affecting git index #33
  which was already up-to-date.

But of course it still depends on #33.

[rfay]

I don't know if in my fork I want to support both styles of installation, or just using my Composer project template. I was initially thinking I'd support both, if it's not too much faff.

All I care about here is using a "normal" database type, and having drush available. I'm pretty sure your template is a fine way to do that, true?

[joachim-n]

Yup, but what I mean is if I drop support for running this directly in a Drupal core clone, then none of #33 is needed.

[rfay]

Again, any way you get drush works for me :)

[joachim-n]

@rfay is it intentional that this is still using the sqlite DB for running PHPUnit tests?

[rfay]

Actually, this was using mariaDB by accident until a recent PR. But IMO it should use mariaDB by default and allow using any supported database. That's actually why I started working on this PR a bit, because I wanted to see "real" performance comparisons on Drupal, comparing DB types. I think it's possible that the use of sqlite3 "for performance reasons" may be obsolete.