feat(linter/jsx-a11y/anchor-has-content): add options to match eslint

[cellison-figma]

Description

Eslint supports a components option for jsx-a11y/anchor-has-content that specified additional components to treat as anchor elements. This adds equivalent support for that option.

Note: I am not certain if this is something that should instead be read off of settings.jsx-a11y.components, as that could list { MyAnchor: 'a' }. Doing that would enable implicit application of rules to custom components based on rendered entity, but that may be the wrong use case, as the custom component definition itself could be responsible for rendering required children.

AI disclosure

I used GPT 5.6 Sol to assist in implementation of this fix. I've reviewed all generated code and test coverage.

[codspeed-hq]

Merging this PR will not alter performance

✅ 5 untouched benchmarks
⏩ 71 skipped benchmarks¹

---

_{Comparing cellison-figma:feat/jsx-a11y-anchor-has-content-options (0e97575) with main (ebf7d18)}

Footnotes

1. 71 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cellison-figma]

@camc314 anything I can do here to help get this merged?

[camc314]

thanks!

[camc314]

Note: I am not certain if this is something that should instead be read off of settings.jsx-a11y.components, as that could list { MyAnchor: 'a' }. Doing that would enable implicit application of rules to custom components based on rendered entity, but that may be the wrong use case, as the custom component definition itself could be responsible for rendering required children.

looks unnecessary - the upstream implementation doesn't do thi