refactor(transformer/styled-components): store block name in arena

[overlookmotel]

In some circumstances, block_name can be inserted into AST in many places. So put it in arena, and reuse the same string over and over, rather than creating a new arena string each time.

Sorry @Dunqing! It was me that said store it as a String. I was wrong!

[overlookmotel]

• perf(transformer/styled-components): pass Atom instead of Option<Atom> #12218
• refactor(transformer/styled-components): use Atom everywhere #12217
• refactor(transformer/styled-components): store block name in arena #12216 👈 (View in Graphite)
• refactor(transformer/styled-components): shorten code #12215
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #12216 will not alter performance

_{Comparing 07-11-refactor_transformer_styled-components_store_block_name_in_arena (0c08c37) with 07-11-refactor_transformer_styled-components_shorten_code (5fffa96)}

Summary

✅ 34 untouched benchmarks

[Dunqing]

I thought I had misunderstood what data should have been stored in the arena all along —thank goodness you spotted I was correct here!

[graphite-app]

Merge activity

• Jul 11, 3:26 PM UTC: Dunqing added this pull request to the Graphite merge queue.
• Jul 11, 3:36 PM UTC: Merged by the Graphite merge queue.