AEM Cloud sites configuration properties merging from config.publish to config.publish.stage

When specific property is not explicitly deifned under config.publish.dev, the system automatically merges/inherits the property value defined under config.publish. 

Steps to Reproduce:

1. Create a configuration with few values under config.publish.dev.
2. Create a configuration with the same PID as defined earlier under config.publish, and update the values, include new property which was not defined as part of config.publish.dev.
3. Deploy to cloud dev environment.
4. Observe that the dev environment uses the value from config.publish while there is existing configuration file for config.publish.dev without any vlaue for the new property.

This issue occurs on all runmodes.

As per this document https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/configuring-osgi#runmode-resolution,

There is no property-level merging between runmode specific folders for the same PID. AEM selects only one configuration which is having most matching runmodes.

Please let me know if anyone encountered the same.

Thanks,

Sravani