INF-2227: Add documentation for COManage CO Group provisioning.

[williamnswanson]

No description provided.

[mwestphall]

I was able to follow this document to add a new COManage Group, looks good.

[brianhlin]

I've got thoughts on formatting but will have to provide details at a later time

[brianhlin]

See in-line comments. Mostly nit-picky stuff to adhere to our style guide: https://osg-htc.org/technology/documentation/style-guide/. Make sure to batch commits together when accepting suggestions (https://osg-htc.org/technology/software/git-software-development/#batch-commits-when-accepting-suggestions-from-a-review)

Also as a heads up, you should basically never submit PRs from your main / master branches as the default PR behavior is to allow the maintainer to add commits to your PR, i.e. your fork's main / master branch

[brianhlin]

Suggested change

	it must first be provisioned.
	it must first be provisioned.

You don't need the leading space here as the newline will be replaced by a space (unless there are multiple newlines)

[brianhlin]

Suggested change

	==============================
	================

Just for visual alignment of the article title

[brianhlin]

Suggested change

	A collection of step-by-step instructions for common actions for use by administrators of the OSG COManage.
	A collection of step-by-step instructions for OSG COmanage administrators.

Just a little bit of brevity here. Also, the appropriate capitalization is COmanage

[brianhlin]

Suggested change

	COManage Recipes
	COmanage Recipes

[brianhlin]

Suggested change

	Steps for Common COManage Actions
	----
	This section contains some common actions administrators perform on the OSG COManage, and how to do so.

All of this basically just repeats what you say in the sentence above. Also, adding a section level here adds noise to the section hierarchy and it's not entirely clear why we need it (if we have another section in this doc at the same level, what would it actually be?)

[brianhlin]

Suggested change

	- On COManage, navigate to `Configuration` -> `Clusters` -> `Configure` -> `Manage Unix Cluster Groups`
	-> `+ Add Unix Cluster Group`
	- Select the name of the Group you are trying to provision from the drop-down menu, then click `ADD`
	1. On COManage, navigate to `Configuration` -> `Clusters` -> `Configure` -> `Manage Unix Cluster Groups`
	-> `+ Add Unix Cluster Group`
	1. Select the name of the Group you are trying to provision from the drop-down menu, then click `ADD`

[brianhlin]

Suggested change

	1. #### Provision group
	### Provision group

[brianhlin]

Suggested change

	- In the `PROVISIONED SERVICES` tab of the Edit page for the Group,
	click the `⚙ Provision` button, then on `Provision`.
	
	If all prior steps have been completed, you should get a message that the Group was successfully provisioned.
	In the `PROVISIONED SERVICES` tab of the Edit page for the Group, click the `⚙ Provision` button, then on `Provision`.
	
	If all prior steps have been completed, you should get a message that the Group was successfully provisioned.

There aren't multiple actions to take here so you don't need to toss this under a list

[brianhlin]

Suggested change

	In order for a CO Group from COManage to show up in LDAP (and thus be made available for reference on Hosts),
	In order for a CO Group from COManage to show up in LDAP (and thus be made available for reference on hosts),

Adding a linebreak between the heading and content for readability, not sure why hosts was capitalized

[brianhlin]

I think it'd be worth adding an admonition here to speak to the fact that OIDC clients needing groups don't need any of these steps outside of the group creation (see https://osg-htc.org/technology/documentation/style-guide/#notes and https://squidfunk.github.io/mkdocs-material/reference/admonitions/#supported-types)