Track PostTypeCheckSemanticChecks.CheckImplFile activity.

[nojaf]

Description

Related to #14429.
While playing around with https://gist.github.com/nojaf/b9f642eec283482fc720ac9cac95e9af to find out what could be improved, it was interesting to see that PostInference takes more time than the type-checking. (For this single example of course)

I'd like to track PostTypeCheckSemanticChecks.CheckImplFile in the future.

Checklist

• Test cases added

• Performance benchmarks added in case of performance changes

• Release notes entry updated:

  Please make sure to add an entry with short succinct description of the change as well as link to this pull request to the respective release notes file, if applicable.

  Release notes files:

  • If anything under src/Compiler has been changed, please make sure to make an entry in docs/release-notes/.FSharp.Compiler.Service/<version>.md, where <version> is usually "highest" one, e.g. 42.8.200
  • If language feature was added (i.e. LanguageFeatures.fsi was changed), please add it to docs/releae-notes/.Language/preview.md
  • If a change to FSharp.Core was made, please make sure to edit docs/release-notes/.FSharp.Core/<version>.md where version is "highest" one, e.g. 8.0.200.

  Information about the release notes entries format can be found in the documentation.
  Example:

  • More inlines for Result module. (PR #16106)
  • Correctly handle assembly imports with public key token of 0 length. (Issue #16359, PR #16363)
    *while! (Language suggestion #1038, PR #14238)

  If you believe that release notes are not necessary for this PR, please add NO_RELEASE_NOTES label to the pull request.

[github-actions]

⚠️ Release notes required, but author opted out

Warning

Author opted out of release notes, check is disabled for this pull request.
cc @dotnet/fsharp-team-msft

[vzarytovskii]

Thanks, that's nice to have more activity events!

[vzarytovskii]

Wondering if when we building compiler with Proto compiler, we can automatically collect statistics and attach it to PR via comment. Will it be helpful?

[T-Gro]

An invokable GH action would be nice, for timing the self-built.
The --times output was already adjusted to be markdown, and I think we could sneak in some markers to make it better grep-able if it isn't already out of the box.