[video_player]Added HTTP headers setting to video_player plugin

[Yarikk26]

Not the best solution for flutter/flutter#16466 especially for iOS.
It seems that there is the only one way to set headers for iOS player, but it isn't public (https://stackoverflow.com/a/23713028).

[Yarikk26]

@JohnGalt1717 You can add something like this into your pubspec.yaml:

video_player:
  git:
    url: https://github.com/tvip/flutter-plugins.git
    ref: videoplayer_http_headers #branch or commit hash here
    path: packages/video_player

You can also specify branch tvip in ref field. There are some more additions from me in that branch, but it's a bit outdated(feb 2019). There is the one more way: you can fork this repo and merge my changes into yours copy and use it. :)

[praxder]

I'm also very interested in getting widevine and fairplay working. Any updates on when this might get merged?

[dvirgiln]

I really need this functionality as well. This PR has been open for one and a half years. Any idea when this will be merged?

[vishnukvmd]

FWIW, react-native-video ran into a similar issue, and decided to go ahead with an implementation using the AVURLAssetHTTPHeaderFieldsKey, similar to what's proposed here: TheWidlarzGroup/react-native-video#2014

I'd say that this is a pragmatic way to solve this problem.

[stuartmorgan]

We apologize for the long delay in triaging this PR. We’re in the process of overhauling our PR triage system to respond much more quickly, as well as working through the backlog.

We’re currently working through a large backlog of PRs. As explained in CONTRIBUTING.md, votes for the corresponding issue are the primary way we’re prioritizing non-trivial reviews; this addresses a fairly highly-voted issue, so is something we can work on moving forward. In order for that to happen, the PR will need:

• Updating to changes in plugin structure on master (e.g., federation)
• Tests (at least unit tests of the app-facing->plugin interface portion of the change)

@Yarikk26 If you're still interested in moving forward with this, once you've done the above please comment and I'll route this to a reviewer. If not, perhaps someone else will be interested in taking over in a new PR.

[stuartmorgan]

Given the lack of response to the last comment, and the new PR, I'm going to close this in favor of the new PR.