Inline some element methods for better stack overflow affinity

[goderbauer]

Fixes #73730.

Locally, this reduced the stack_size benchmark by 30% in release mode at the expense of slightly higher binary size. Example binary increase for the Gallery app on android-arm64:

• libapp.so (the Dart AOT) increased by 53.9 KB (+0.2%) uncompressed
• the overall APK increased by 15.0 KB (+0.02%) compressed

A local spot check with the gallery transition perf benchmark did not reveal any notable changes in build performance.

Last, but not least, this allows developers to nest more widget before facing a stack overflow. In a test setup, an additional ~900 containers could be nested before a stack overflow occurred.

See also #73730 for details on the points discussed above.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

[goderbauer]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

The test for this is the stack_size benchmark: https://flutter-flutter-perf.skia.org/e/?queries=sub_result%3Dstack_size_per_nesting_level.

[Hixie]

Does this affect the stack traces in error messages in any significant way?
What about the logic for folding stack traces?

[goderbauer]

This change is transparent to stack traces. The VM already inlines methods based on internal heuristics without affecting stack traces and we just tell it to be more aggressive in inlining these annotated methods.

[goderbauer]

Updated PR description with some more information on the size increase.

[tvolkert]

LGTM