Fix patch permissions

[harshach]

Describe your changes:

Patch operations must be evaluated in hierarchical order.
For ex: if a User is adding a owner or tag they can be
/owners/0/displayname, /owners/0/fullyQualifiedName or /messageScheam/schemaFields/order/tags
in first case we should look up owners and return the operation immediately if try to match operation with the path
then we will get user might not have permissions edit_display_name

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[github-actions]

Phylum OSS Supply Chain Risk Analysis - FAILED

This repository analyzes the risk of new dependencies. An
administrator of this repository has set requirements via Phylum policy.

If you see this comment, one or more dependencies have failed Phylum's risk analysis.

Package: braces@2.3.2 failed.

braces@2.3.2 is vulnerable to Uncontrolled resource consumption

Risk Domain: Software Vulnerability
Risk Level: high

Reason: Critical or High software vulnerability

Package: braces@3.0.2 failed.

braces@3.0.2 is vulnerable to Uncontrolled resource consumption

Risk Domain: Software Vulnerability
Risk Level: high

Reason: Critical or High software vulnerability

View this project in the Phylum UI

[sonarcloud]

Quality Gate passed for 'open-metadata-ingestion'

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