DSPO Should provide a role for the end user to utlize for long term programmatic access.

The usecase is if frontend, or workbench team wants to hand out permissions to a user or SA via rolebinding, they can bind to this role provisioned via DSPO for a particular DSPA. The role should be created by DSPO in this case, because domain knowledge of backend is required and permissions are contingent on how DSPO implements oauth proxy. Thus any update to oauth proxy permissions, would always need to be reflected in this role.

Some considerations as part of this task that we want to verify as well:

• Confirm that using a route is better than using a service for allotting access to dsp (via oauth proxy)
• https://issues.redhat.com/browse/RHODS-7423