docs: native*Tracks options are no longer needed

[squarebracket]

Description

I believe using native*Tracks: false is no longer needed since #76, but this crept back into the docs.

Specific Changes proposed

Remove native*Tracks: false from the overrideNative sections of the README.

Requirements Checklist

• Feature implemented / Bug fixed
• If necessary, more likely in a feature request than a bug fix
  • Unit Tests updated or fixed
  • Docs/guides updated
  • Example created (starter template on JSBin)
• Reviewed by Two Core Contributors

[gkatsev]

It may be necessary depending on the browser you're using maybe? Like I think that it was necessary for Legacy Edge?
@mister-ben do you remember anything about it? I think you dealt with these options "recently".

[squarebracket]

@gkatsev I think you're referring to this?

[squarebracket]

It seems that the line was removed from the README, but not from the code snippet.

[gkatsev]

Yeah, that was probably it.

[gkatsev]

This comment seems to imply it's still needed? #920 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gkatsev]

Well, just noticed that Chrome 85 (85.0.4183.121) on macOS has audio tracks now which causes the native audio track to show up. The workaround right now is to enable nativeAudioTracks: false. So, I think this is still needed.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.