header-minimal: replace disable-headings prop with enable-headings prop

[powellkerry]

Are you removing, renaming or moving a folder in this PR?

• [ x] No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• [ x] Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

The component library has updated the va-header-minimal component to not render heading elements by default. To do this the disable-headings prop has been replaced with the enable-headings prop. This update is to adjust for that change.

Related issue(s)

department-of-veterans-affairs/vets-design-system-documentation#3097

Testing done

local testing using proxy-rewrite

Screenshots

No visual changes

What areas of the site does it impact?

Minimal header

Acceptance criteria

Quality Assurance & Testing

• [ x] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• [ x] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• [ x] Linting warnings have been addressed
• [ x] Documentation has been updated (link to documentation *if necessary)
• [ x] Screenshot of the developed feature is added
• [ x] Accessibility testing has been performed

Error Handling

• [ x] Browser console contains no warnings or errors.
• [ x] Events are being sent to the appropriate logging solution
• [ x] Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• [ na ] Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?