shfmt and shellcheck for a few more files

[seefood]

Description

picked a few completions and plugins at random and cleaned them up with shellcheck and shfmt

How Has This Been Tested?

passed to the CI after pre-commit was happy

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• If my change requires a change to the documentation, I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
• I have added tests to cover my changes, and all the new and existing tests pass.

[cornfeedhobo]

@seefood Would you like some help with reviews? I'm concerned about these failing tests and how much code is getting merged and self-reviewed right now.

[seefood]

@seefood Would you like some help with reviews? I'm concerned about these failing tests and how much code is getting merged and self-reviewed right now.

I would love some. Noah gave me maintainer rights to release some of the pressure, and I merged the easy stuff that was stuck, but most of what remans are the trickier stuff that's got some bitrot, and some of it needs manual merges, while others are maybe no longer relevant.

the issue with BATS complaining about too few tests running - I have no idea why iot happens yet, I have not dived into that yet.

[cornfeedhobo]

My memory with BATS is fuzzy, but I think when BATS complains about too few tests running, it means the test environment is broken and/or a test has failed.

Would you like to open a PR to start fixing the tests before merging much more stuff?

[seefood]

@cornfeedhobo I never used bats and won't have time to get into it before next year, so if you know how t fix it, be my guest.