Refactor the internal config code to use new TedgeConfig

[reubenmiller]

Is your refactoring request related to a problem? Please describe.

A new TedgeConfig internal feature was introduced in #1936. This should be utilized by all components and the older configuration model should be removed.

Describe the solution you'd like

• Refactor existing code base to make use of TedgeConfig

  • tedge-mapper Refactor tedge-mapper by using new tedge config API #2013
  • tedge-agent tedge-agent must use new tedge-config #2073
  • tedge-firmware-plugin Refactor plugins by using new TEdgeConfig API #2064
  • tedge-configuration-plugin Refactor plugins by using new TEdgeConfig API #2064
  • tedge-log-plugin Refactor plugins by using new TEdgeConfig API #2064
  • tedge Refactor tedge to use new config #2077

• Remove the older configuration logic

Describe alternatives you've considered

Additional context

[reubenmiller]

@didier-wenzek Do we need to complete the last task in the list before closing the ticket, or is this outdated information?

[didier-wenzek]

@didier-wenzek Do we need to complete the last task in the list before closing the ticket, or is this outdated information?

This outdated. I forgot to update it after #2143