fix(kuma-cp): change way of setting if resource is read only

[lukidzi]

Changed how we check if a resource should be read-only. Previously we were allowing only Dataplane resources to be edited on the zone, now we are checking if the resource is synchronized and in which direction.

If we are on Global:

• and resource is synchronized from Global
• or resource is not synchronized
• or resource is synchronized from Global and from Zone
  we allow you to edit it from global.

If we are on Zone:

• and resource is synchronized from Zone
• or resource is not synchronized
• or resource is synchronized from Global and from Zone
  we allow you to edit it from Zone.

• Link to docs PR or issue --
• Link to UI issue or PR --
• Is the issue worked on linked? --
• The PR does not hardcode values that might break projects that depend on kuma (e.g. "kumahq" as a image registry) --
• The PR will work for both Linux and Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Unit Tests --
• E2E Tests --
• Manual Universal Tests --
• Manual Kubernetes Tests --
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? --
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

[lukidzi]

@Mergifyio backport release-2.0

[mergify]

backport release-2.0

✅ Backports have been created

• #5348 fix(kuma-cp): change way of setting if resource is read only (backport #5345) has been created for branch release-2.0