MS-941/MS-1058 Update sync configuration to the new structure

[luhmirin-s]

JIRA ticket
Will be released in: 2025.3.0

Notable changes

• CoSync changes introduced additional changes to project configuration, and since the sample upload config also relies on the same version, baseline config changes for both features have to be implemented more or less together. This PR contains only the changes in the existing configuration structure and does not add any co-sync specific fields:
  • synchronization.down properties moved to dedicated synchronization.down.simprints object. All usages are redirected to Simprints' specific config. For now the down.simprints is considered non-optional since it is used across modules. @BurningAXE I leave it to you to make it optional when adding co-sync configuration.
  • synchronization.frequency moved to synchronization.down.simprints.frequency and synchronization.up.simprints.frequency. All usages are defaulted to the "down.simprints" frequency, unless it explicitly requires "up".
  • Due to the frequencies being in multiple places, the enum has been moved to the upper level in all layers (domain, proto and API)
• Did not add any co-sync configuration fields. @BurningAXE, that part is for you to implement.
• This PR is based on sample upload prep work and therefore assumes that the samples config changes have been merged already (relevant for property indexes in proto files)

Testing guidance

• Run the app, attempt configuration sync.
• Install an older version, sync the config, then update to this PR and sync the config again.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[ybourgery]

This is an optional field now, have you not done it because you will let Milen doing it?

[luhmirin-s]

Reading swagger schemas in GDocs is a bit confusing, and I missed the optional part. Anyhow, I will leave this detail to Milen, since making it optional would require a bunch of changes in the business logic across the app that are not directly related to any of the features I am working on. I just needed the configuration parsing in a working state.

[ybourgery]

Did not add any co-sync configuration fields, and simprints.up.destinations is assumed to always be Simprints (and therefore ignored).

FYI this field synchronization.up.destinations has been deprecated since 2022.2.0 and would not be used to configure the down sync source, it would just be the presence of synchronization.down.simprints or synchronization.down.commcare

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
89.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud