Long-term solution for semantically correct headers

[akegan]

As a part of addressing #142 in #1450, there were issues with the InfoCard having header levels that jumped by more than one level from the outside to the inside of the card. As you can see from this comment we just updated the info card to an h3 to fix the errors for now, but the longer term fix is to make the header level configurable as a prop on the component so that the level can be semantically correct in any other context

More info about this a11y rule

Acceptance Criteria

1. Add a prop to InfoCard to set the title header level, default to a reasonable level
2. Look for other components where the header level might need to be configurable as a prop for them to fit correctly into the context of a page.