Update Docker Image to Ubuntu 24.04 ( Noble )

[pentatonicfunk]

• Update docker image to use Ubuntu 24.04 ( noble )
  -- Add missing noble repository list
  -- Hacky fix of pip shyaml install on Ubuntu 24.04: see https://pimylifeup.com/python-externally-managed-environment/
• Update mariadb repo to OVH ( only on focal and noble ): see unable to provision using several providers on Arm64/Apple Silicon M3 chip #2727 (comment)
• Introduce vvv_get_mysql_service_name, in attempt to improve mariadb vs mysql service inconsistency
  -- Unable to replicate the service name inconsistency, but it happened. ref: Slack #docker
• Minor output copy fixes / improvements
• Introduce customizable general.php_cli_version
  -- It does have use case for me personally at least
  -- Generally this provides user with better control of PHP CLI version rather than meddling / replicating vvv_restore_php_default to change PHP CLI version: https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org/blob/main/docs/en-US/adding-a-new-site/changing-php-version.md?plain=1#L83

Checks

• I've updated the changelog.
• I've tested this PR: Partially
• This PR is for the develop branch not the stable branch.
• This PR is complete and ready for review.

Note on testing:

• Currently i only have linux host testing machine. I've tested with Docker provider, and it went okay, logs attached
• Tried using Virtualbox, but it keeps timing out / error

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

• If anyone can help testing it, please

Changelogs:

• Please advise

[update-docs]

Thanks for opening this pull request! Make sure CHANGELOG.md gets updated with this change, additionally any docs that need updated can be found at https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org

GitHub

GitHub - Varying-Vagrant-Vagrants/varyingvagrantvagrants.org: The VVV docs and website

The VVV docs and website. Contribute to Varying-Vagrant-Vagrants/varyingvagrantvagrants.org development by creating an account on GitHub.

[tomjn]

@pentatonicfunk how much of this can we split into separate PRs? Upgrading Ubuntu isn't a small task but adding the sources could be done and released pretty quickly to simplfy merging. Likewise some of the other changes are useful and quick to test on their own.

I am mindful that upgrading Ubuntu the last time resulted in some weirdness that needed investigation.

Also, the service changes, I was thinking of changing how services are restarted to use a VVV specific function to insulate against service and systemctl since there's a lot of duplication going on

[pentatonicfunk]

i will try to cherry picks into separate branches next week.

[tomjn]

Running this locally with:

act -j 'on-docker' --container-architecture linux/arm64 -P ubuntu-24.04=ghcr.io/catthehacker/ubuntu:act-24.04

[tomjn]

TLDR the symlinks were the problem

[tomjn]

@pentatonicfunk it's been a long time coming but I think it's time to merge

[welcome]

Congrats on merging your first pull request!