fix: add device.csr_path to cloud profiles

[Ruadhri17]

Proposed changes

As mentioned in #3413 user could not specified device.csr_path per cloud profile. This PR appends multi profile config with csr_path and replaces old approach of accessing config value in tedge cert create-csr.

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

• device.csr_path can't be used under cloud profiles #3413

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

[codecov]

Codecov Report

Attention: Patch coverage is 32.14286% with 19 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
.../tedge_config/src/tedge_config_cli/tedge_config.rs	34.61%	10 Missing and 7 partials ⚠️
crates/core/tedge/src/cli/certificate/cli.rs	0.00%	2 Missing ⚠️

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
583	0	3	583	100	1h38m58.468912999s

[rina23q]

Waiting for a system test. Can be added under /tests/RobotFramework/tests/tedge/certificate_signing_request.robot

[rina23q]

Why --output_path option is removed?