Fix visual issues with the services json schema form

[richard-cox]

• Text can overlap in the service json schema form
  • Requires changes to upstream schema form component
  • 
• You could mention that, aside from the overlap, there should be more vertical separation among the fields (between the description of a field and the title of the next one… so that it's clear what title/description belongs to what field

[Lucsantosg]

Here is an illustration of the suggestions above for the purpose of:

• Ensuring enough vertical separations to group visually the title/value/description pertaining to a given field/paramter, so that they don't overlap with the following field/paramter
• The description text (appearing below the field value) appears left-aligned in some fields, but not in others. Making them left-aligned consistent would help distinguish it from the titles

Note also that the Instance Name parameter duplicates (and, thus, could conflict) with the main instance Name (at the top of the page.

[gberche-orange]

@Lucsantosg

Note also that the Instance Name parameter duplicates (and, thus, could conflict) with the main instance Name (at the top of the page.

This conflict actually comes from a "instance name" service parameter declared by the service broker in its catalog json schema.

Confusion could potentially be reduced by having a box around service parameters to group them together, as well as offering the ability to display the json schema with hint such as "Learn more about this form" when a json schema is associated to the service plan.