Remove stale opcheck xsuccess entries (jagged/sparse/quantize)

[q10]

Summary:
generate_opcheck_tests records a "xsuccess" status when a previously-failing opcheck
variant now passes -- i.e. the entry is stale and should be removed. Removing these
de-clutters the failures dicts and drops the problematic-test count with zero
behavioral risk (the tests already pass). 12 stale xsuccess entries removed:

• jagged: fbgemm::jagged_index_select (KeyedJaggedIndexSelectTest aot_dispatch_dynamic
  • faketensor for test_keyed_jagged_index_select_dim1) -> {}
• sparse: fbgemm::generic_histogram_binning_calibration_by_feature (4),
  fbgemm::group_index_select_dim0 (2), fbgemm::segment_sum_csr (2) -> {}
• quantize: fbgemm::FloatToFP8RowwiseQuantized (2) -> {}

Emptied keys are left as {} per the existing convention for healthy ops. Legitimate
xfail entries (data-dependent / dynamic-output-shape variants) are untouched.

Part of the fbgemm_dev test-health remediation for T191384137.

Reviewed By: henrylhtsang

Differential Revision: D107927030

[meta-codesync]

@q10 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D107927030.