Don't abort on ddev release show changes when no changes are found

[alopezz]

What does this PR do?

Stops ddev release show changes from aborting when no changes have been found, so that it retains behavior that other commands rely upon.

Motivation

AITS-247

Aborting causes the application to exit regardless of context, which is a problem when that breaks expectations of other commands that rely on invoking this command directly.

This was causing release make all to abort early as soon as an integration didn't have a change. This regression was introduced in #15378; we weren't aborting under that scenario before.

Additional Notes

Longer term, I think we should try to avoid invoking commands from within any sort of minimally complex logic, and be careful with where we call functions that can exit the interpreter completely. We can leave this as it is for now until we move this to the ddev package. There's also a couple of unused options that could be removed when we do that as well.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Changelog entries must be created for modifications to shipped code
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

[codecov]

Codecov Report

Merging #15932 (e360bd7) into master (ac52e8b) will increase coverage by 0.10%.
The diff coverage is n/a.

Flag	Coverage Δ
activemq	?
cassandra	?
datadog_checks_dev	82.51% <ø> (+0.07%)	⬆️
hive	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
presto	?
solr	?
tomcat	?

Flags with carried forward coverage won't be shown. Click here to find out more.

[github-actions]

Test Results

    4 files      4 suites   4m 19s ⏱️
418 tests 418 ✔️   0 💤 0 ❌
936 runs  903 ✔️ 33 💤 0 ❌

Results for commit e360bd7.