User Story

As a customer of ROSA/OSD, I use the htpasswd idp for adding several users at once, sometimes across several interactions.
I need to be able to both interactively and non-interactively add more than one user to the htpasswd idp.

As a OSD or ROSA cluster administrator, I'd like to utilize htpasswd as an IDP, just as well as it can be in OCP. I'd like to plug in the yaml config for the htpasswd oauth provider through the OCM UI and it should populate in my cluster to enable htpasswd. 
This should allow me to map more than just the single admin user as its implemented currently.

For each product, documentation will need to be added for this IDP.
For this feature, OCM UI will need to be updated to accomodate.

This feature also needs to be enabled & supported with our ROSA Terraform content.

-------------------

We should offer this through accepting a file (yaml file? htpasswd generated file?) and as CLI options perhaps like this...

rosa create idp --type=htpasswd -c cluster --fromfile=myhtpassfile
rosa create idp --type=htpasswd -c cluster --user=adejong,password1 --user tavni,password2 --user=byron,password3
rosa edit idp --type=htpasswd -c cluster --user=adejong,password1 --user tavni,password2 --user=byron,password3

This must work both interactively and non-interactively. This involves allowing full CRUD (create read update delete) of htpasswd idp users.

This cannot break existing htpasswd or create-admin functionality.

Acceptance Criteria

1. users can create the htpasswd IDP by passing in a htpasswd file
2. users can create the htpasswd IDP by passing in an array of users and password