chore: reverting to use of xmlns https back to http

[awentzel]

Description

Using xmlns="https: is invalid for files on CDN or that are referenced as a link. If they are embedded in HTML as text it's fine, which is what I think webpack does for most of our images.

Reference: https://stackoverflow.com/questions/18467982/are-svg-parameters-such-as-xmlns-and-version-needed

Motivation & context

favicons are broken after recent updates. This will revert those changes and set back to correct.

Issue type checklist

• Chore: A change that does not impact distributed packages.
• Bug fix: A change that fixes an issue, link to the issue above.
• New feature: A change that adds functionality.

Is this a breaking change?

• This change causes current functionality to break.

Adding or modifying component(s) in @microsoft/fast-components checklist

• I have added a new component
• I have modified an existing component
• I have updated the definition file
• I have updated the configuration file

Process & policy checklist

• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.

[EisenbergEffect]

I don't think this should matter really as the xmlns isn't typically looked up. I think it can technically even be a custom scheme.