OwlViT/Owlv2 post processing standardization

[qubvel]

What does this PR do?

Standardize OwlViT and Owlv2 post-processing

1. Add post_process_grounded_object_detection method for Processor (+ deprecation for post_process_object_detection method)

def post_process_grounded_object_detection(
    self,
    outputs,
    threshold: float = ...,
    target_sizes: Optional[Union[TensorType, List[Tuple]]] = None,
    text_labels: Union[List[str], List[List[str]]] = None,  # <------------- new keyword arg
)

2. Add text_labels for post-processed output (if text_labels are provided as a keyword argument for post_process_grounded_object_detection). It's already mapped text names for detected bounding boxes.

For a full description regarding standardization see #34926

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline,
  Pull Request section?
• Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[qubvel]

Hey @molbap! Please review if you have bandwidth!

[qubvel]

Not related changes, just refactoring

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[molbap]

Nice standardization, just added a comment related to documentation :) also wondered if you could get away with a is_grounded boolean arg and just have one method, or even an Enum with either grounded, guided or default values, if that makes sense

[molbap]

would it make sense to add some documentation for post_process_image_guided_detection as well in addition to post_process_grounded_object_detection, just to show usage? Also, the underlying method isn't deprecated IIUC, so would need to still be documented

[qubvel]

Yes, thanks for the suggestion! Added documentation for the method in b13c68c

[qubvel]

I would prefer to leave it as separate methods. This way, it is more consistent with other post-processing methods like post_process_object_detection, post_process_image_segmentation, etc., and there is no need to overcomplicate the code with more if/else code paths.

[qubvel]

@ArthurZucker please review when you have bandwidth

[ArthurZucker]

LGTM sorry for putting it off for so long! 🤗

[ArthurZucker]

cool to move away from single letter variables