[RuntimeAsync] Make JitOptimizeAwait not a release switch.

[VSadov]

A trivial change.

Closes: #115264

The switch may still be useful for testing/investigating issues, but not as interesting in benchmarking. Thus does not need to be release switch.

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull Request Overview

This PR makes JitOptimizeAwait a regular JIT configuration option instead of a release-only switch and updates the importer to apply await optimization by default in release builds.

• Changed the configuration macro for JitOptimizeAwait in jitconfigvalues.h
• Updated importer.cpp to remove the release-only guard around JitOptimizeAwait

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/coreclr/jit/jitconfigvalues.h	Changed JitOptimizeAwait from a RELEASE_CONFIG_INTEGER to an OPT_CONFIG_INTEGER
src/coreclr/jit/importer.cpp	Wrapped the JitOptimizeAwait() check under #ifdef DEBUG, enabling the optimization in release

Comments suppressed due to low confidence (2)

src/coreclr/jit/jitconfigvalues.h:587

• [nitpick] Since JitOptimizeAwait is now a regular configurable option, consider updating any related documentation or comments to reflect its broader availability beyond release switches.

OPT_CONFIG_INTEGER(JitOptimizeAwait, "JitOptimizeAwait", 1) // Perform optimization of Await intrinsics

src/coreclr/jit/importer.cpp:9105

• Removing the runtime check for JitOptimizeAwait() in release causes impMatchTaskAwaitPattern to run on every async method, which may impact JIT throughput; please benchmark or consider retaining a lightweight guard.

                    if (compIsAsync())

[VSadov]

/ba-g Android timeout