cronet : Update library + Move to StableAPIs in Cronet

[Ashok-Varma]

In this Pull Request

1. Cronet is updated to 119.6045.31 from 108.5359.79, In which Experimental API's are deprecated and moved to Stable Interfaces.
2. grpc-cronet Moved Experimental API's to Stable Interfaces
3. Removed use of reflection as Experimental API's are no longer in use (which are introdced in cronet: use reflection to load and invoke experimental APIs in ExperimentalBidirectionalStream.Builder #6111)

Minor Changes

1. Updated JavaDoc : Android Permission from MODIFY_NETWORK_ACCOUNTING (deprecated) to UPDATE_DEVICE_STATS
2. Update to JAVA-8 API's to improve code readability
3. Moved from Charset.forName("UTF-8") to StandardCharsets.UTF_8 Standard

Fixes #10396 (@sergiitk)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Ashok-Varma / name: Ashok Varma (cb2e1af, 42ff5a4, e728136, ed457b5)

[Ashok-Varma]

Hi @sergiitk / @ejona86 / @temawi,

I've updated changes in to different commits. It's open for review

[Ashok-Varma]

Hi @sergiitk,

I was just wondering on Linux and Macos artifacts taking time (those are stalled for ~10 days), does it signify any problem in the builds ? or are we supposed to generate and add them ?

[ejona86]

This looks fine to me, but I'm not sure if enough Android devices have the stable API. We may need to fall-back to the experimental API to reach more devices. @temawi, would you be able to investigate that?

[ejona86]

I was just wondering on Linux and Macos artifacts taking time (those are stalled for ~10 days), does it signify any problem in the builds ?

It's not a problem. We have to manually start those builds by adding that kokoro label.

[Ashok-Varma]

This looks fine to me, but I'm not sure if enough Android devices have the stable API. We may need to fall-back to the experimental API to reach more devices. @temawi, would you be able to investigate that?

I agree to this, Adding little-bit of background :

• ExperimentalAPI deprecation done on Oct 27, 2022
• Any Custom Implementation of Cronet (if API is not yet updated), Needs to update the API +move the experimental implementations to CronetEngine.
• All Googles cronet implementations (embedded, fallback, play-services) are compatible with new API.

[temawi]

This looks fine to me, but I'm not sure if enough Android devices have the stable API. We may need to fall-back to the experimental API to reach more devices. @temawi, would you be able to investigate that?

I agree to this, Adding little-bit of background :

• ExperimentalAPI deprecation done on Oct 27, 2022
• Any Custom Implementation of Cronet (if API is not yet updated), Needs to update the API +move the experimental implementations to CronetEngine.
• All Googles cronet implementations (embedded, fallback, play-services) are compatible with new API.

I also checked with the Cronet team - this should be a safe change to make.

[ejona86]

@temawi, given the commits are split out, we'll probably want to rebase this instead of squashing (ideally the commits would have cronet: prefixes to make scanning easier, but this is fine).

[Ashok-Varma]

@temawi, given the commits are split out, we'll probably want to rebase this instead of squashing (ideally the commits would have cronet: prefixes to make scanning easier, but this is fine).

Updated commits with cronet: prefix

[Ashok-Varma]

Thank you @temawi and @ejona86 for the help on PR.
Any plans on next release date, What's the release cadence for gRPC ?

[ejona86]

@Ashok-Varma, see the milestones. Minor releases are scheduled every six weeks.