[QDQ] Add shared qdq selectors

[YUNQIUGUO]

Description: Describe your changes.

This is one of the first steps of NNAPI QDQ Integration: (step 3 in this pr description #10052)

• Add a shared SelectorManager object which extracted selectors related logic from the original selectionactiontransformer.
• Add sample test for usage demonstration.

[skottmckay]

If we'll generally be looking up a specific operator version, an unordered_map may be a better fit than a vector.

[YUNQIUGUO]

thought operatorsetversion would be a set of ints.. Can you clarify how would this unordered_map be used/how does the map key/value look like?

[guoyu-wang]

This line is already updated in here

onnxruntime/onnxruntime/core/optimizer/qdq_transformer/selectors_actions/qdq_selector_action_transformer.cc

Lines 56 to 58 in 2078210

	qdq_selector_action_registry.RegisterSelectorAndAction(action_name,
	{{"AveragePool", {}},
	{"LeakyRelu", {}}},

To avoid the fork of the code, can we keep them in a single place for these keys?
For example, some shared function to return this OpVersionsMap (without alias)

static const std::unordered_map<std::string, std::vector<ONNX_NAMESPACE::OperatorSetVersion>> GetUnaryOpVersionsMap() {
    return {{"AveragePool", {}},{"LeakyRelu", {}}};
}

[YUNQIUGUO]

Updated. Add some static methods for this.

[edgchen1]

will qdq_selector_action_transformer.cc be updated to use the same helpers?

[YUNQIUGUO]

thanks for the reminder. will keep them updated together later.

[skottmckay]

Things are going to diverge so I don't think we should try and keep it in sync with the CPU EP's QDQ SAT.

The QDQ node group selectors for use by other EPs are looking for all QDQ node groups. The CPU EP is looking for things it has QLinear implementations for.

Additionally the CPU EP will be registering NodeSelector based classes in SelectorAndAction. The QDQ node group selectors will be registering NodeGroupSelector based classes.

So they will look somewhat similar initially but I expect as we keep expanding the ops we match as QDQ node groups that won't be for long.

e.g. SoftMax should be matched in NNAPI but not the CPU EP. Similarly we currently have only Add and Mul, however (afaik) there's no reason Sub and Div shouldn't be matched and those can easily be added to the NodeGroupSelector registrations.

[edgchen1]

this one should be first

[edgchen1]

sorry, to clarify, I meant it should be the very first include. the rationale for this is to ensure that the related header can be included on its own and not require other external includes before it.

[skottmckay]

Some documentation for non-trivial public methods would be good.

e.g. Initialize is self-explanatory. GetQDQSelections could provide a quick overview of what happens. Imagine you're a new developer trying to understand what the class does. Without that info you're forced to read the entire implementation of the method to know this. That's both time consuming and potentially error prone if something in the implementation is misinterpreted.

[skottmckay]

[guoyu-wang]

nit, can be more concise, can be updated in a later PR

if (qdq_node_group_selection) {
      qdq_selections.push_back(*qdq_node_group_selection);
}

[guoyu-wang]

nit, can try to combine this test case with the QDQ_Selector_Test test case
Can be updated in a later PR