Update access control how-to guide

[ppbaena]

Description of the change

Update the How-to guide to standardize with rest of guides and follow style guidelines.

Benefits

Documentation updated

Possible drawbacks

N/A

Applicable issues

• related to Review and adapt existing Kubeapps documentation to comply with new guidelines #5024

[netlify]

✅ Deploy Preview for kubeapps-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	8fc42c7
🔍 Latest deploy log	https://app.netlify.com/sites/kubeapps-dev/deploys/633ee71934f5e600094f0e7a
😎 Deploy Preview	https://deploy-preview-5433--kubeapps-dev.netlify.app/docs/latest/howto/access-control
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[castelblanque]

Suggested change

	1. [Read access to Applications within a namespace](#read-access-to-applications-within-a-namespace) 2.[Write access to Applications within a namespace](#write-access-to-applications-within-a-namespace)
	1. [Read access to Applications within a namespace](#read-access-to-applications-within-a-namespace)
	2.[Write access to Applications within a namespace](#write-access-to-applications-within-a-namespace)

[ppbaena]

I have used the format document option in Visual Studio before saving it, so this could change that. Thanks!

[castelblanque]

Please note that most part of the Assigning Kubeapps User Roles section only applies to direct Helm.
For example <RELEASE_NAME>-repositories-read and <RELEASE_NAME>-repositories-write are only created if the plugin is Helm and value rbac.create is true (defaults to true).
We might want to add a section per plugin on how to manage access. The mentioned content would go inside direct Helm plugin, and for Carvel and Flux we might point to any existing documentation those projects might have (haven't checked).

[castelblanque]

Thanks!