when adding reconciled configlets to the list of configlets to be applied, users can define it anywhere in the list, cvp-backend correctly moves it always to the end of the list as it should, however it detects a change (even if it could be a no-op change) and triggers a task (which can be an empty task)
### Steps to reproduce
```shell
Simply running a playbook similar to above where the reconciled config is put anywhere besides the bottom of the list (last index) will result with a task generated, which in case of a no-op change should not happen
Issue Summary
when adding reconciled configlets to the list of configlets to be applied, users can define it anywhere in the list, cvp-backend correctly moves it always to the end of the list as it should, however it detects a change (even if it could be a no-op change) and triggers a task (which can be an empty task)
Which component(s) of AVD impacted
cv_device_v3
How do you run AVD ?
Ansible CLI (with virtual-env or native python)
Input variables
Relevant log output
Code of Conduct