c8y-configuration-plugin supported configuration types is not updated via cloud update

[reubenmiller]

Describe the bug

Adding a new configuration type and then applying the new c8y-configuration-plugin.toml file via a Cumulocity IoT operation does not update the list of support configurations in Cumulocity.

The test passes in version 0.10.0 (prior to the refactoring), and fails afterwards. The refactoring was done in #1828.

Note: Restarting the c8y-configuration-plugin does update the supported configurations in Cumulocity IoT, however this is not the expected behaviour.

To Reproduce

The regression was discovered in PR to add the integration tests: #1875

The failing test case is shown below:

Property	Value
Source	configuration_operation.robot
TestCase	Update configuration plugin config via cloud

Expected behavior

Adding a new supported configuration type should be possible by applying a new c8y-configuration-plugin file type, and the new type should be visible in the Cumulocity IoT UI without having to restart the service.

Screenshots

Environment (please complete the following information):

• OS [incl. version]: Debian 11
• Hardware [incl. revision]: Docker
• System-Architecture [e.g. result of "uname -a"]: arm64 (aarch64)
• thin-edge.io version [e.g. 0.1.0]: 0.10.0-68-g63e33c09

Additional context

[reubenmiller]

Update: Rebasing from main has fixed the cloud update handling, though some questions about some other inotify events are still being clarified before closing the ticket.

• Handle in-place edits via sed, e.g. sed -i 's/CONFIG1/CONFIG3/g' /etc/tedge/c8y/c8y-configuration-plugin.toml
• Handle overwriting a file via move, e.g. mv /etc/tedge/c8y/c8y-configuration-plugin-updated.toml /etc/tedge/c8y/c8y-configuration-plugin.toml

[reubenmiller]

Closing as this original problem was solved by rebasing the PR's branch. The additional gaps in the inotify events will be covered in #1896