feat: auto inject completions

[35C4n0r]

Pull Request Title

Automate Shell Completion Configuration

Description

Adds automatic injection of the autocomplete script into the appropriate shell profile and then instructing the user on how to source the file (or instruct to open a new terminal).

Type of Change

• 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 not work as expected)
• This change requires a documentation update

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

Related Issue(s)

This PR addresses issue #49
Closes #49
/claim #49

Screenshots

Notes

Please add any relevant notes if necessary.

[35C4n0r]

@Tpuljak PR is ready for review.

[Tpuljak]

@35C4n0r the changes regarding the autocompletion injection look great.

Before I approve, please remove the contributors commit from this PR and add it as a separate PR (example).

[35C4n0r]

@Tpuljak removed that commit.

[35C4n0r]

@Tpuljak contributors PR here #150

[35C4n0r]

@Tpuljak pushed the changes that fixes that issue 👍🏻

[35C4n0r]

@Tpuljak made the required changes.
PS: sorry for making you review so many times 😅

[Tpuljak]

The code is now inline without codebase and the command does update the profile with the completion script. Good work!

The issue now is that the completion script does not seem correct.

For me, the completion script just autocompletes paths when called.

For example:

daytona c + TAB does not suggest daytona create but simply fills in a directory that starts with c.

If it works for you as intended, let me know. If not, please look into this.

@idagelic might be useful in this conversation. He implemented completions for one of our other CLI tools.

[35C4n0r]

@Tpuljak It works fine for Bash + Fish + ZSH (Manual + new shell).

[Tpuljak]

@35C4n0r you're right. I can confirm that the completions work.

The issue I mentioned above was related to my Warp terminal. All good. Approving the PR.

[Tpuljak]

Awesome work!

[idagelic]

This looks good, thanks for the PR @35C4n0r !

The Cobra default "completion" command prints out the completion script results to stdout. Users might expect this behavior and use it for some custom shell profile configs. Should we leave this option to the user but perhaps just hide it from help to avoid confusion using spf13/cobra#1541 ?

In that case there would be no unexpected behavior to the user and we could rename this new command to "autocomplete" just as the go file is called. Does this make sense to you? @Tpuljak

[35C4n0r]

@idagelic made the required changes.

[idagelic]

Thank you @35C4n0r