Arm backend: Add experimental support for new TOSAQuantizer

[AdrianLundell]

Allows initializing TOSA/EthosU/Vgf quantizers with use_composable_quantizer=True to use a new implementation of the quantizer following the Cortex-M. See
#17701 for more details.

• Creates a new temporary TOSAQuantizer API layer for switching between the two versions
• Adds a TOSAQuantizationConfig encapturing TOSA-specific qspec requirements for certain ops.
• Adds quantizer_support.py for defining what operators are supported by the quantizer.
• Align mark_node_as_annotated in cortex-m backend to TOSAQuantizer behaviour.
• Update quantizer reporter to handle TOSA qspecs as they are dynamically created.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18100

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 0cd9609 with merge base c81126e ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zingo]

Hi @SS-JIA / @digantdesai this adds a file, do you want/need to check this?
This is also something we would like to get into 1.2 if possible.

[AdrianLundell]

Fails unrelated

[rascani]

_LAZY_IMPORTS?

[AdrianLundell]

This is a workaround since the import situation is a bit messy with imports across the cortex-m and arm backend. The idea is to clean this up when things have stabilized, I didn't want to move things in this commit to make the diff cleaner, I hope this is OK.

[digantdesai]

I like the overall direction, and the Cortex-M quantizer reuse. Also the priority for the composition.
I will let RJ review and stamp, as I am still catching up.

One thing I would say is, add an e2e test with both Ethos and Cortex-M quantizers and run the test on FVP.

[AdrianLundell]

I hope this is what you had in mind for the test @digantdesai, we have also run all tests internally with the new quantizer set to true sucessfully. The idea is that we can let you and others try this out and give feedback and then there should be minimal disruption as we flip the flag to True as default.

[meta-codesync]

@rascani has imported this pull request. If you are a Meta employee, you can view this in D96368239.

[rascani]

Ok, finally gotten it all the rest of the way through. Thank you for sorting out the lazy imports, that resolved a lot of it. There were still a few more buck rules that needed fixing up, but there were also usages of some Quantizer APIs that no longer existed.

I think this should do it.

[digantdesai]

Review automatically exported from Phabricator review in Meta.