[CBBS] Improve Import and Create repository components for Cloud

What needs to be done?
We need to improve the Import and Create repository components (the ones with input fields) as currently they don't provide the best UX.

The issues that I have noticed:
1. It should be clear what "S3 Force path style" means and when it should be used (use cases and how to determine if you need to use it would be a good improvement, an example of a "compatible technology" would be a nice thing to have as well).
2. It should be clear that "Staging Directory" refers to a local storage directory (even with the hint it is not explicit). May be changing this to "Path To Local Staging Directory" or "Local Staging Directory" or something similar could make this more clear?
3. "Cloud Bucket" is a bit confusing since it seems to assume that the cloud provider that the user chooses refers to it's storage containers as "buckets" (I assume this is due to the fact that AWS was the first provider that we added support for). We need to change this to something more general and improve the hint to explain what this refers to in the context of AWS/S3/Azure.
4. "Path Prefix" is also a bit confusing, an example would be a great improvement (may be a name change for the field as well, as it is not clear what it is a prefix to).
5. "Cloud Auth Type" could be renamed to "Cloud Authentication Method" or just " Authentication Method" as this is not much more verbose (not sure about this).
6. "Credential ID" and "Credential Key" have examples for AWS but not other providers, this should be added.
7. Clarify that "Region" is only required for AWS in addition to removing the field when other providers are selected (nitpick).
8. More verbose names that I suggested above can go into the input fields themselves as this is done for "ID" and "Location" (greyed out values that are displayed when a field is empty).

I will add/remove improvements if necessary.