Image Segmentation pipeline
# What does this PR do?
## TLDR
Implements `image-segmentation` pipeline (for [DetrForSegmentation](https://huggingface.co/transformers/model_doc/detr.html#detrforsegmentation) atm). 
## API specifications
Input: image source (identical to the input of `image-classification` & `object-detection` pipelines)
Output:
```python
List(Dict(
    mask: str, # base64 str
    label: float,
    score: int,
))
```

### Two design choices I've made and would like to discuss (& modify if needed):
1. Output `png_string` has masks information using same mechanism as COCO panoptic segmentation annotations. See section `4. Panoptic Segmentation` from https://cocodataset.org/#format-data. Paraphrasing a bit:
> per-pixel segment ids are stored in the PNG string. Each segment is assigned a unique id. Unlabeled pixels (void) are assigned a value of 0. Note that when you load the PNG as an RGB image, you will need to compute the ids via ids=R+G*256+B*256^2.
2. Image segmentation pipeline accepts `subtask` arg. There are different variations of segmentation task (semantic, instance, panoptic, etc. see image below). If a model doesn't implement requested subtask, it gets defaulted to what's available. See example below:
https://github.com/huggingface/transformers/blob/dd5c2697f129988bd9c70b52555e49dd32c78bd2/src/transformers/models/detr/feature_extraction_detr.py#L738-L739
<img width="400" src="https://user-images.githubusercontent.com/48327001/126451023-4edd68e4-c552-422a-9765-297a470d36c6.jpg">

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/master/CONTRIBUTING.md#start-contributing-pull-requests),
      Pull Request section?
- [x] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
      Discussed in huggingface/hub-docs#43, huggingface/hub-docs#6, https://github.com/huggingface/huggingface_hub/pull/378
- [x] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/master/docs), 
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/master/docs#writing-source-documentation).
- [x] 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.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- albert, bert, xlm: @LysandreJik
- blenderbot, bart, marian, pegasus, encoderdecoder,  t5: @patrickvonplaten, @patil-suraj
- longformer, reformer, transfoxl, xlnet: @patrickvonplaten
- fsmt: @stas00
- funnel: @sgugger
- gpt2: @patrickvonplaten, @LysandreJik
- rag: @patrickvonplaten, @lhoestq
- tensorflow: @LysandreJik

Library:

- benchmarks: @patrickvonplaten
- deepspeed: @stas00
- ray/raytune: @richardliaw, @amogkam
- text generation: @patrickvonplaten
- tokenizers: @n1t0, @LysandreJik
- trainer: @sgugger
- pipelines: @LysandreJik

Documentation: @sgugger

HF projects:

- datasets: [different repo](https://github.com/huggingface/datasets)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Examples:

- maintained examples (not research project or legacy): @sgugger, @patil-suraj
- research_projects/bert-loses-patience: @JetRunner
- research_projects/distillation: @VictorSanh

 -->

#### Update 1:
Updated output shape:
```python
List(Dict(
    mask: str, # base64 str
    label: float,
    score: int,
))
```
The goal for any segmentation architecture is to implement the most detailed version of segmentation subtask they can so that other subtasks can be reconstructed (if needed). For example, if an architecture post_process_segmentation method implements part-aware panoptic, other subtasks (including semantic, instance, etc.) can be reconstructed from part-aware panoptic output since all the details needed are in there
Please let me know if I should merge this PR @Narsil @NielsRogge @LysandreJik <|||||>It's gtg for me.