Review codebases for use of experimental APIs

[ianbotsf]

In a few places our code uses Kotlin APIs marked as experimental or unstable. We should review all usages of thusly-marked APIs and determine if there's a path off of them to more stable implementations before GA. All repositories should be reviewed.

In scope are at least the following annotations:

• @DelicateCoroutinesApi
• @ExperimentalContracts
• @ExperimentalCoroutinesApi
• @ExperimentalStdlibApi
• @ExperimentalTime
• @ExperimentalUnsignedTypes
• @FlowPreview
• @InternalCoroutinesApi

Successful outcome of this task would be, for each instance of using APIs marked as experimental/unstable, one of the following resolutions:

• Plan to migrate away to new API or implementation
• Continue using with justification (e.g., usage is in low-risk area like tests or codegen)

[aajtodd]

kotlin.time is in focus for stabilization, hopefully this stabilizes soon...

[lauzadis]

kotlin.time is in focus for stabilization, hopefully this stabilizes soon...

Based on this changelog it should be coming in 1.9.0, I asked in KotlinLang Slack and they said "Yes. This includes time sources, time marks, and measureTime functions"

[aajtodd]

Closing as I believe this work was completed (see linked PRs)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.