fix #3135 adding support for patchStatus and detection of patch type

[shawkins]

Description

Fix for #3135 - adding mock support for a json patch of status, and rejecting other patch types.

I could not find existing json merge or strategic merge logic in the existing dependencies. It looks like jakarta.json-api provides a json merge patch utility - but it seems easier for now to just return an unsupported status.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[centos-ci]

Can one of the admins verify this patch?

[iocanel]

LGTM

[manusa]

LGTM, thx!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

90.5% Coverage
0.0% Duplication

[victornoel]

@shawkins @manusa any way to get those changes in 5.4.2 maybe? See #3267 :)

[manusa]

Hi @victornoel
5.5.0 has already been released and doesn't include significant breaking changes. Is there any specific reason why you would need this back-ported?

[victornoel]

@manusa actually, no reason no, I think we can safely ignore my earlier request, I will be using 5.5.0! Thx again :)

[manusa]

I will be using 5.5.0!

🚀 cool!