Add a test to make sure `ddev-hostname` is working properly in CI

[stasadev]

We have DDEV_NONINTERACTIVE=true for all our tests, which means that we don't actually test if ddev-hostname works correctly (because it usually asks for a password).

But in CI environments, like GitHub Actions, sudo runs without a password, which makes this testing possible.

We should add a new test (run it only in GitHub Actions), which should:

• set DDEV_NONINTERACTIVE=""
• run ddev config --auto && ddev start && curl https://site.ddev.site
• run ddev config --project-tld=test && ddev start && curl https://site.test (we can use something different instead of *.test, i.e. random letters)

I implemented some testing for --project-tld=test here, but we need better test coverage:

• feat: add testing for DDEV HEAD github-action-setup-ddev#57

Related issue:

• v1.24.9: Unable to reach project URL in CI when using custom project_tld #7790

[rfay]

It's not completely true that passwordless sudo is always available. I turned that off in our own buildkite runners (or at least most of them) because I found it allowed me to make the assumption that passwordless sudo would work, and of course in the real world it doesn't.

[rfay]

This should attempt this test only if passwordless sudo is available. That can be determined with sudo true for example.