Resolve AMP issues on sam-autocomplete

[trandrew08]

Description

• Pulling in the same changes to autocomplete-search.component.html to resolve AMP issues on sam-autocomplete.
• Per new ARIA 1.2 guidelines (which is still in drafting stage), they are acknowledging the problem and are recommending that we remove the wrapper.

https://www.w3.org/TR/wai-aria-1.2/#substantive-changes-since-the-wai-aria-1-1-recommendation

Motivation and Context

Type of Change (Select One and Apply Github Label)

• Bug fix (non-breaking change which fixes an issue) -> Apply bugfix label
• New feature (non-breaking change which adds functionality) -> Apply enhancement label
• Breaking change (fix or feature that would cause existing functionality to change) -> Apply breaking label

Screenshots (if appropriate):

Which browsers have you tested?

• Internet Explorer 11
• Edge
• Chrome
• Firefox
• Safari

Checklist:

• I have read the (https://github.comv/GSA/sam-ui-elements/blob/CONTRIBUTING.md)[CONTRIBUTING.md] document.
• My code passes the automated linter.
• This code has been reviewed by another team member and passes the reviewer checklist found in (https://github.comv/GSA/sam-ui-elements/blob/CONTRIBUTING.md)[CONTRIBUTING.md]
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code is 508 compliant as tested by AMP and JAWS
• Any dependent changes have been merged and published in downstream modules

[trandrew08]

@yerramshilpa @davereed Please review. This is making the sam-autocomplete component the same as autocomplete-search component for 508 compliance.