MODCPCT-87 API versions update

[dmytrokrutii]

MODCPCT-87

According to the epic https://folio-org.atlassian.net/browse/FOLIO-4044, some permissions have been changed in the source-manager-job-executions v3.4 and source-storage-source-records v3.5

mod-copycat uses the following outdated permissions:

"change-manager.jobexecutions.put"
"source-storage.sourceRecords.get" 

New permission	API
"change-manager.jobExecutions.jobProfile.item.put"	/change-manager/jobExecutions/{id}/jobProfile
"source-storage.source-records.collection.get"	"/source-storage/source-records"

Merge this pull request at the same time when the other modules merge the permission rename pull requests:

• MODSOURCE-796 Cleanup permissions mod-source-record-storage#646
• MODSOURMAN-1222 Refactoring permissions mod-source-record-manager#931

[MikeTaylor]

Please use "replaces" so that this is not a breaking change.

[dmytrokrutii]

Please use "replaces" so that this is not a breaking change.

New permissions in mod-source-record-storage and mod-source-record-manager already have the "replaces" keyword.
However, this does not negate the need to change the names in all the affected modules.

Taras Spashchenko:

And yes, if you change the permission name, you must change all references to the old name throughout the FOLIO in all repositories.

You also can see this folio-org/mod-data-import#337 (comment)

@MikeTaylor

[julianladisch]

Please use "replaces" so that this is not a breaking change.

Only the owning module can use "replaces". mod-copycat is not the owner of the changes permissions. The owners already have "replaces" for them.

[julianladisch]

Looks good, thanks!

[julianladisch]

@MikeTaylor Please review you approval rejection.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud