Re-evaluate use of `PublishReadyToRun=False`

Once https://github.com/dotnet/runtime/issues/101866 is resolved, we should publish this as ReadyToRun and measure the startup time differences. If they are significantly better, it may be worth the executable size increase. In my testing, publishing as R2R added about 5MB to the size of the binary.

Start by checking the publish configuration that sets PublishReadyToRun=False and review dotnet/runtime#101866. Once that issue is resolved, publish with ReadyToRun enabled and compare startup time and executable size; the work is done when the measurements support either keeping the current setting or updating it.

Written by the indexing model from the issue text.