Create DesiredConfigFetcher and ConfigToApplyBuilder in RemoteDevelopment::WorkspaceOperations::Reconcile::Output

Issue: Shadow run: create kubernetes manifest in works... (#538163 - closed)

What does this MR do and why?

This MR creates couple of classes to introduce shadow run of Create::DesiredConfig::Main.main class.

• DesiredConfigFetcher is responsible for fetching desired_config. It tries to fetch the desired_config from the database but in case it cannot find it there, it calls Create::DesiredConfig::Main.main function.
  • Currently the data is persisted only in test environment. This condition will be removed later as part of Persist desired kubernetes configuration on wor... (#541907 - closed)
• ConfigToApplyBuilder is responsible for injecting secrets and filter out non-applicable objects from desired_config. It uses DesiredConfigFetcher class to fetch the desired_config.
• ResponsePayloadBuilder calls ConfigToApplyFetcher that calls ConfigToApplyBuilder and OldDesiredConfigGenerator and performs #diff on both. It logs the diff in case it is not empty but returns the older config_to_apply in both the cases.

References

Issue: Shadow run: create kubernetes manifest in works... (#538163 - closed)

Screenshots or screen recordings

This MR does not contain any UI changes.

How to set up and validate locally

These changes are not yet plugged in any flow. Run smoke-test for sanity

scripts/remote_development/run-smoke-test-suite.sh 

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.