Compilation benchmarks and artifacts size threshold

Now that we are leaning toward using procedural macros where appropriate, And with the addition of all the generated code we use, It would be wise to add some sort of CI step to time our compilations and prevent merge without acknowledgment if changes cause significant slow-down.

This would be hard since getting rid of variants on GitHub CI agents might prove to be a difficult problem to solve.

The other one(artifact size) is much easier to implement and has an immediate effect on how we develop, It would be awesome if we get to know how much each PR affects our build size so we can make informed decisions between performance and binary size, Everyday things like inlining and/or declarative macros are the areas which gain the most from this information.

The issue does not name files, tests, or CI entry points. Begin by locating the repository's CI configuration and build artifact workflow, then define how artifact-size changes and compilation slowdowns should be reported; done means pull requests expose these measurements and significant changes receive acknowledgment.