Add CI minimal build with all options disabled. Fix python binding code if sparse tensors are disabled.

[skottmckay]

Description:
Add CI builds that check the code compiles with all the optional features disabled.

Those are:

              --disable_exceptions \
              --disable_ml_ops \
              --cmake_extra_defines onnxruntime_DISABLE_SPARSE_TENSORS=ON \
                                    onnxruntime_DISABLE_OPTIONAL_TYPE=ON \
                                    onnxruntime_ENABLE_ORT_FORMAT_RUNTIME_GRAPH_OPTIMIZATION=OFF \
                                    onnxruntime_BUILD_UNIT_TESTS=OFF 

Fix the python binding code when DISABLE_SPARSE_TENSORS is defined.

Motivation and Context
Validate options used by 1P partners compile cleanly.

[edgchen1]

this could probably move between 7a and 7b (possibly also after 7b in case we ever add more steps). steps 6a and 6b shouldn't update the code with any op exclusions.

[skottmckay]

Doing it this way is a little more consistent as it matches the pattern of doing a cleanup, even if not strictly necessary, between each main step.

This way you only have to think about additional cleanup needs within a step (i.e. between the 'a' and 'b') and don't require knowledge across steps. I shouldn't need to know everything that happened within 6a and 6b to decide if cleanup is necessary or not before step 7.

Not needed between 7a and 7b as they're both disabling all ops.

Adding it after feels unnecessary as we may never add another step.

[edgchen1]

my interpretation of the pattern was that each numbered step (including 'a', 'b') that modifies the source cleans up after itself before the next numbered step.
I think this works though

[yuslepukhin]