pkgs/ok_http: DevTools Networking Support.

[Anikate-De]

Items in this PR:

• Add profiling enabled/disabled test groups
• Create Kotlin callback RedirectReceivedCallback to allow Dart code to operate on redirect responses (crucial for HTTP Profiling)
• Create client_profile_test.dart (re-used from cronet_http)
• Added necessary implementation in ok_http_client to support DevTools
• Updated CHANGELOG.md

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[brianquinlan]

In a follow-up PR, would it make sense to migrate the redirect logic to Dart? Actually, would it make sense to make interceptors available in Dart?

Taking a step back, maybe you'd want to expose OkHttpClient or a wrapper around that to Dart?

With that users can control caching, connection pools, DNS, etc.

I'm not sure what the best way to do that is though.

[Anikate-De]

About migrating the redirection logic to Dart, there are issues with threading while implementing Interceptor.
Hossein and I have been trying to work our way around this issue, but so far, RedirectInterceptor stands out as an example.

---

About exposing configurations to users, I had planned to provide high-level functions (and constructor parameters) within OkHttpClient allowing users to tweak the client according to their requirements.

For example, if a user wants to alter the timeout for a request, they can either pass the timeout duration in the constructor or in the function:

class OkHttpClient extends BaseClient {
  late bindings.OkHttpClient _client;
  OkHttpClient([Duration? timeoutDuration]) {
    // creates a client based on the timeout and assigns it to _client
  }
  void setTimeout(Duration timeoutDuration) {
    // uses a new builder from `_client` and edits its timeout
  }

But yes, a wrapper sounds good! We can use the architecture that CronetEngine has.