Very applicable to calculated fields

I just added these as a was a bit creeped out seeing people do
name address merges without visibility on wheter the address
was a real address or a pseudo-address

This addresses #10 - which is a tricky issue to replicate although I was
managing semi-reliably with the contact creates in that issue.

This addresses something I hit in testing where the display name was an email & I got
a js error

I think it was used before we improved the rest of the output

There is some ambiguity about it - it should be string but is sometimes an array so this
handles both

This updates to match the breaking change proposed for 5.35 in https://github.com/civicrm/civicrm-core/pull/19438

```html
<!-- Old attribute notation -->
<div MY-SUBFORM="..."></div>

<!-- New element notation -->
<MY-SUBFORM options="..."></MY-SUBFORM>
```

typos

This allows location pre-cleaning & prioritisation - which can solve  odd merge issues

- postal_code_suffix
- diacritics
- mixed casing (Smith vs SMITH)

@colemanw made changes to afform that meant I couldn't set hidden fields using passed options
any more & I also found that shoreditch uses an old version of bootstrap so my expections of how accordian
should work were wrong without getting later bootstrap