role attribute not being used on version 3

[jnavb]

Describe the bug
role attribute not being used on version 3

Reproducible test case

    <FontAwesomeIcon
      icon={...}
      role="button"
    />

svg is rendered with role="img"

Expected behavior
svg should be rendered with role="button"

Desktop (please complete the following information):

• Browser All
• Version 3

Additional context
Add any other context about the problem here.

[charles4221]

I don't believe this is a common pattern, since generally if the icon is acting as a button you would wrap the icon with a more semantic element for that purpose like

<a title="Email me" role="button">
  <FontAwesomeIcon icon="envelope" />
</a>

or

<button aria-label="Email Me">
  <FontAwesomeIcon icon="envelope" />
</button>

I do note that this was possible in 0.2.x, so I can still look into it if there's enough strong need, but I still believe going with a built-in semantic option makes better sense than treating the actual svg element as a "button" instead of what it really is (img) for users with accessibility needs.

[jnavb]

Having this kind of breaking change in a v0 version is understandable. I’ll try to see if I can migrate it.

If nothing changes, I’d then advocate for updating the TypeScript types. As it stands, it gives the impression that we can still pass all HTMLSvgProps through the FortAwesome React component, like before. Updating that and making clear what can actually be passed would be really helpful for next upgrades