sync dispatcher immutable files with Dispatcher SDK and image v2.0.191

[krystiannowak]

sync dispatcher immutable files with Dispatcher SDK and image v2.0.191

Description

Since the previous sync of dispatcher immutable files with Dispatcher SDK and image was from version 2.0.166 in March 2023 and AEM CS releases already progressed further, including dispatcher image and SDK tooling containing newer files, it resulted already in customer using latest public AEM CS releases being out of sync and reporting issues like adobe/aem-project-archetype#1043

Hence we propose to sync those files with the ones from the latest Dispatcher SDK and image v2.0.191 in order for validation scripts not to fail in immutable files compatibility check step as described in https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug.html?lang=en#third-phase

Related Issue

• AEMaaCS SDK and archetype compatibility aem-project-archetype#1043
• Updating archetype dispatcher.cloud configuration to version 2.0.191 aem-project-archetype#1141

Motivation and Context

Not to fail immutable files validation step described in https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug.html?lang=en#third-phase when using Dispatcher SDK tooling from the latest AEM CS releases.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[krystiannowak]

@davidjgonzalez @SachinMali this PR probably would need your review?

cc: @froesef