Apply tiering's call counting delay more broadly (dotnet/coreclr#18610)

Apply tiering's call counting delay more broadly (dotnet/coreclr#18610)

Apply tiering's call counting delay more broadly

Issues
- When some time passes between process startup and first significant use of the app, startup perf with tiering can be slower because the call counting delay is no longer in effect
- This is especially true when the process is affinitized to one cpu

Fixes
- Initiate and prolong the call counting delay upon tier 0 activity (jitting or r2r code lookup for a new method)
- Stop call counting for a called method when the delay is in effect
- Stop (and don't start) tier 1 jitting when the delay is in effect
- After the delay resume call counting and tier 1 jitting
- If the process is affinitized to one cpu at process startup, multiply the delay by 10

No change in benchmarks.

Commit migrated from https://github.com/dotnet/coreclr/commit/6b403ca4422f2bf3df9d25a32790cc4c0d4b6ee4