feature: Stricter permission/condition fallback mechanism for isGranted

[heueristik]

Description

This PR removes the fallback functionality ( two logical ORs ||)

function isGranted(address _where, address _who, bytes32 _permissionId, bytes memory _data) public view virtual returns (bool) {
  /*(1)*/ _isGranted(_where, _who, _permissionId, _data) ||
  /*(2)*/ _isGranted(_where, ANY_ADDR, _permissionId, _data) ||
  /*(3)*/ _isGranted(ANY_ADDR, _who, _permissionId, _data);
}

from isGranted in PermissionManager as it could lead to unintuitive behavior.
The new behavior is as follows (excerpt from the docs):

Moreover, if a condition is set, we return its isGranted result and do not fall back to a more generic one. The condition checks occur in the following order

1. Condition with specific _who and specific where.
2. Condition with generic _who: ANY_ADDR and specific _where.
3. Condition with specific _where and generic _who: ANY_ADDR.

As a bonus, we save gas by, for example, not calling (2) and (3) if (1)already answered false.

Task: OS-710

Type of change

• 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 not work as expected)

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran all tests with success and extended them if necessary.
• I have updated the CHANGELOG.md file in the root folder.
• I have updated the DEPLOYMENT_CHECKLIST file in the root folder.
• I have updated the UPDATE_CHECKLIST file in the root folder.

The base branch was changed.

[Rekard0]

LGTM