fix: optionally load bash completion for npm and nvm, fixes #6106

[stasadev]

The Issue

• ddev npm autocompletion doesn't work #6106

ddev npm completions don't work.

How This PR Solves The Issue

Adds an optional check if the completion function is available, if not: load it again.
I did the same for nvm just in case.

Manual Testing Instructions

ddev npm <tab><tab>

Automated Testing Overview

Release/Deployment Notes

[github-actions]

Download the artifacts for this pull request:

• all-ddev-executables.zip
• ddev-macos-amd64.zip
• ddev-macos-arm64.zip
• ddev-linux-arm64.zip
• ddev-linux-amd64.zip
• ddev-windows-amd64-installer.zip

See Testing a PR.

[rfay]

I think this is as good as it gets.

I don't like all the things it returns sometimes, like ddev npm in <tab>:

$ npm in
in               innit            insta            install-ci-test
info             ins              instal           install-clean
init             inst             install          install-test

But I think those are all a result of npm's behavior. Not sure where ins and inst and instal come from, but I guess super-ambitious npm autocomplete.

nvm looks great.

[stasadev]

Not sure where ins and inst and instal come from

I'm sure developers are tired of typing the full command, or they may type it with errors, and get angry when it doesn't work.

I myself use aliases like stop for ddev stop, and I make typing mistakes, so for this particular case I have:

alias stop="ddev stop"
alias stio="stop"
alias stp\[="stop"
alias sotp="stop"

And I keep typing it wrong, but now it works no matter what 😅