feat: avoid using 444 permissions in example tedge-configuration file

[reubenmiller]

Proposed changes

Use linux permissions 644 instead of 444 as the latter is unexpected for most users as it does not allow users to edit the file, and give that it is the tedge-log-plugin file, then it should be editable for the owner.

This change was initiated after a customer interaction.

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

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

[didier-wenzek]

Approved

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.2%. Comparing base (23c2714) to head (5826ae2).
Report is 10 commits behind head on main.

Additional details and impacted files

Files	Coverage Δ
crates/extensions/tedge_config_manager/src/lib.rs	59.4% <100.0%> (ø)
...rates/extensions/tedge_config_manager/src/tests.rs	91.7% <100.0%> (ø)

... and 11 files with indirect coverage changes

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
453	0	3	453	100	1h10m50.886882s