[video_player] Add cookie support for network resources

[jaysephjw]

Description

I Broke this change up in to 3 parts, #3136 #3137 and #3138. Review each step individually.

Add cookie support for video_player network resources.

Avoids the problem of relying on "AVURLAssetHTTPHeaderFieldsKey" (undocumented ios API) seen in #953 and #897 by only supporting cookies.

Implementation

Dart:
Optionally include a List when calling VideoPlayerController.network
Pigeon these over to hosts via List, which each cookie as a "Set-Cookie" value strings.

iOS:
Parse the strings into NSHTTPCookies and attach them using AVURLAssetHTTPCookiesKey

Android:
Parse the strings into HttpCookies so we can then break name=value pairs back out, and build a "Cookie" header for EXOPlayer

Web:
Set the cookies onto the document with the document.cookie setter, which supports full "Set-Cooke" value strings. Note: Haven't tested web yet. Are these still there after the player disposes? Can we cleanup?

Related Issues

• Implements Video Player plugin - Support HTTP cookies flutter#61638
• Alleviates Video Player plugin - Support HTTP headers flutter#16466 for users who just need a Cookie header

Testing done

Tested on iOS and Android with an HLS server that requires an auth cookie.

Breaking Change

• No, this is not a breaking change.

Checklist

• I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
• I updated/added relevant documentation (doc comments with ///).
• I read and followed the [Flutter Style Guide].
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I signed the [CLA].
• I am willing to follow-up on review comments in a timely manner.
• I have tested on Android
• I have tested on iOS

TODO:

• Test on web
• The analyzer (flutter analyze) does not report any problems on my PR.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
• All existing and new tests are passing.
• I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
• I updated CHANGELOG.md to add a description of the change.

[jaysephjw]

Realized I need to be using the pigeon tool (neat!) to update the courier types instead of by hand (oops!).

Currently blocked on that since I need List, but can't get List to work flutter/flutter#61660

[rohitsharma1113]

Expecting this to get merged anytime soon @jaysephjw ?
Needed the cookies functionality for serving content securely via CloudFront.

[jaysephjw]

@rohitsharma1113 I am hoping to! Updating this today. But have not gotten any review yet.

From looking at previous PRs and feedback from the build system, it looks like I may need to separate PRs out so as to bump the platform_interface first. I'll do that now.

[jaysephjw]

@iskakaushik @cyanglaz can anyone take a look?

[Salakar]

Leftovers of a merge here

[jaysephjw]

Fixed in the child PR #3 : https://github.com/flutter/plugins/pull/3138/files#diff-82e451e154983ecbae7c1dfb22c5dc4324ecd25cc2f7ab9a933e2abf4d14fe4a

[Salakar]

Can I close this PR then in favour of the other 3; #3136 #3137 and #3138?

[jaysephjw]

@Salakar If that's best then yes, whatever makes the most sense to avoid confusion. As a start I updated this PR to have 0 diffs so its obvious the changes are happening elsewhere.

[rohitsharma1113]

Any update on this ?

[jaysephjw]

I may wait for #3281, which updates the pigeon version, before landing this. I'll then push new diffs from the new pigeon version.