feat(core/presentation): Support inline radio buttons

[christopherthielen]

This PR changes the following things in RadioButtonInput:

• adds support for inline radio buttons.
• adds stringOptions prop instead of overloading options which previously took either an array of Option objects or an array of strings (I'm open to feedback on this API change)
• switches from a Set of options to an array, so ordering can be applied.

I'd primarily like feedback from @anotherchrisberry but he's OOO so I'm tagging Erik and Alan.

---

This PR also reverts tweaks to global bootstrap CSS that adjust margins and padding.

before:

after:

---

Finally, this adds support for wrapping of inline checkboxes and radio buttons using a margin hack. This puts the margin between successive elements on the right of the element instead of the left. This is to support wrapping of inline checkboxes and radios.

before:

after:

cc: @Jammy-Louie I believe this component should allow you to drop this duplicate component:

deck/app/scripts/modules/cloudfoundry/src/presentation/forms/inputs/CloudFoundryRadioButtonInput.tsx

Lines 23 to 57 in de57adf

	export const CloudFoundryRadioButtonInput = (props: ICloudFoundryRadioButtonInputProps) => {
	const { value, validation, inputClassName, options, ...otherProps } = props;
	const className = `RadioButtonInput radio ${orEmptyString(inputClassName)} ${validationClassName(validation)}`;
	const RadioButtonsElement = ({ opts }: { opts: Array<Option<string>> }) => (
	<div className="horizontal">
	{opts.map(option => (
	<div key={option.label} className={className}>
	<label className="cloud-foundry-radio-button">
	<input
	type="radio"
	{...otherProps}
	value={option.value}
	checked={option.value === value}
	onChange={e => {
	if (props.onChange) {
	props.onChange(e);
	}
	}}
	/>
	<span className="marked">
	<Markdown message={option.label} />
	</span>
	</label>
	</div>
	))}
	</div>
	);
	if (isStringArray(options)) {
	return <StringsAsOptions strings={options}>{opts => <RadioButtonsElement opts={opts} />}</StringsAsOptions>;
	} else {
	return <RadioButtonsElement opts={options as Array<Option<string>>} />;
	}
	};

[erikmunson]

don't feel like I have enough/any context on the motivation for splitting out stringOptions/options, so no real opinion there.

[erikmunson]

I realize this was already here before the diff, purely curiosity: is this intended for html sanitization/support, actual markdown support, or both?

[christopherthielen]

It's for markdown support

[Jammy-Louie]

When its merged I'll remove the provider specific implementation in favour of this one.

[maggieneterval]

I can't wait to use this, looks great! 🔥