feat: REST API to update entity twin data

[albinsuresh]

Proposed changes

REST API to update entity twin data

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

[codecov]

Codecov Report

Attention: Patch coverage is 91.66667% with 16 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...s/core/tedge_agent/src/http_server/entity_store.rs	92.02%	1 Missing and 10 partials ⚠️
...ates/core/tedge_agent/src/entity_manager/server.rs	89.28%	2 Missing and 1 partial ⚠️
...rates/core/tedge_agent/src/entity_manager/tests.rs	92.30%	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	1h40m32.786878999s

[didier-wenzek]

• It would be good to implement tedge http patch along this PR.
• I was expecting the updated twin data to be published over the twin topics.

[didier-wenzek]

It would be good to tell which key has been rejected.

[albinsuresh]

Resolved by 6e7c4c6

[didier-wenzek]

The example doesn't match the text.

Suggested change

	Update existing fragment: `name`, add new fragment: `hardware` and remove existing fragment: `maintenanceMode` with a `null` value:
	```json
	{
	"name": "Child 01",
	"new-fragment": {
	"new-key": "new-value"
	},
	"extra-fragment": null
	}
	```
	**Example**
	```shell
	curl http://localhost:8000/tedge/entity-store/v1/entities/device/child01 \
	-X PATCH \
	-H "Content-Type: application/json" \
	-d '{
	"type": "Raspberry Pi 4",
	"hardware": {
	"serialNo": "98761234"
	},
	"maintenanceMode": null
	}'
	```
	Update existing fragment: `name`, add new fragment: `hardware` and remove existing fragment: `maintenanceMode` with a `null` value:
	```shell
	curl http://localhost:8000/tedge/entity-store/v1/entities/device/child01 \
	-X PATCH \
	-H "Content-Type: application/json" \
	-d '{
	"name": "Child 01",
	"hardware": {
	"serialNo": "98761234"
	},
	"maintenanceMode": null
	}'

[albinsuresh]

Resolved by 6e7c4c6

[didier-wenzek]

• It would be good to implement tedge http patch along this PR.

I pushed a commit for that: 4e3e940

[albinsuresh]

I was expecting the updated twin data to be published over the twin topics.

Resolved by 6e7c4c6