chore: Fix Rust 1.82 clippy lints

[Bravo555]

Proposed changes

Today, Rust 1.82 was published, which means there are new clippy lints breaking our CI that we get to fix. Yay 🎉

I also fixed lints present on nightly (1.84), so we should be good for a while.

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

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
509	0	2	509	100	1h33m57.391663999s

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
crates/core/tedge/src/bridge/config.rs	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[didier-wenzek]

Approved

[didier-wenzek]

Might be good to attach this definition to a type or a module, rather than remove it.

[Bravo555]

This comment is for EntityTopicId. The struct was moved to another module along with the comment, but the comment in this module wasn't deleted.

thin-edge.io/crates/core/tedge_api/src/mqtt_topics.rs

Lines 275 to 292 in 0748986

	/// Represents an "Entity topic identifier" portion of the MQTT topic
	///
	/// An entity identifier is a fixed 4-segment group, as such any 4 topic
	/// segments that come after the root are considered a part of an identifier,
	/// even if they contain values usually present in the channel group, e.g.
	/// `/m/`.
	///
	/// If the topic ends before the expected 4 segments, the remaining segments are
	/// filled by empty segments (`//`).
	///
	/// # Example
	/// - topic: `te/device/dev1/service/myservice/m//my_measurement`
	/// - entity id: `device/dev1/service/myservice`
	///
	/// # Reference
	/// https://thin-edge.github.io/thin-edge.io/next/references/mqtt-api/#group-identifier
	#[derive(Debug, Clone, Hash, PartialEq, Eq, Deserialize, Serialize)]
	pub struct EntityTopicId(String);