feat: install tedge tab completions during installation

[reubenmiller]

Proposed changes

Install the shell completions during the tedge post installation phase if the detected shell scripts are found.

Adding the script as part of the installation allows for a more seamless completion experience as sometimes no setup needs to be done if the user has already enabled shell completion for their preferred shell.

The system test image now includes the shell completion out of the box to help developers during testing and demos.

Note: The shell completion script is added as part of the post installation and not a static file as the clap generated script will use the full path to the binary that called the tedge completions command which makes running at build time problematic as it would use the build time path of the tedge binary instead of the destinations path.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

• Include shell completions scripts in linux packages for debian and rpm #3405
• Generate shell completions for tedge CLI #3331

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
585	0	3	585	100	1h32m22.818836999s

[didier-wenzek]

Approved.

I only checked things related to zsh.

[reubenmiller]

Approved.

I only checked things related to zsh.

Though the system tests include all three shells (bash, zsh and fish) and the profile changes are part of the container definition, so any system test can be used to try it out.

[rina23q]

Small correction in docs.