Documentation on "Enabling Role-Based Access Control Using XACML" has multiple issues to be fixed

Description:
There are two (2) issues already reported related to this doc in [1] and [2] which are not fixed yet. Apart from those, there are another set of mistakes to be corrected.

Affected Product Version:
APIM 4.1.0

Steps to reproduce:

1. Step 3 asks to add permissions to the webuser role. We do not have any affect on permissions from APIM 4.0.0 onwards. Instead, this step should ask the user to map the webuser role with the Internal/subscriber role, using the role alias feature as mentioned in [3].
2. Step 7 states " , select drop down options as Subject , is/are , at-least-one-member-of in order and enter admin in the last field. Click the icon next to END shown below to configure the attribute value and attribute source to retrieve the user roles from the user store. ".
   However, in the corresponding screenshot [4], it shows Subject , is not/are not , equals which is wrong. The screenshot should be updated here.

Related Issues:

• https://github.com/wso2/docs-apim/issues/5422
• https://github.com/wso2/docs-apim/issues/3309

[1] https://github.com/wso2/docs-apim/issues/5422
[2] https://github.com/wso2/docs-apim/issues/3309
[3] https://apim.docs.wso2.com/en/latest/administer/managing-users-and-roles/managing-permissions/#role-alias
[4] https://apim.docs.wso2.com/en/4.1.0/assets/img/learn/define-entitlement-rules.png

Start by reviewing the APIM 4.1.0 documentation page, the role-alias reference in [3], and the screenshot linked in [4]. Check related issues 5422 and 3309 before editing; done means correcting step 3, aligning the step 7 screenshot with its text, and addressing the documented issues.