add interhand 2d dataset

[liuxin9608]

No description provided.

[codecov]

Codecov Report

Merging #202 into master will decrease coverage by 0.39%.
The diff coverage is 84.88%.

@@            Coverage Diff             @@
##           master     #202      +/-   ##
==========================================
- Coverage   83.52%   83.13%   -0.40%     
==========================================
  Files         107      112       +5     
  Lines        6357     6446      +89     
  Branches     1024     1025       +1     
==========================================
+ Hits         5310     5359      +49     
- Misses        850      896      +46     
+ Partials      197      191       -6     

Flag	Coverage Δ
unittests	83.13% <84.88%> (-0.40%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
mmpose/datasets/__init__.py	100.00% <ø> (ø)
mmpose/datasets/datasets/top_down/__init__.py	100.00% <ø> (ø)
...datasets/datasets/top_down/topdown_coco_dataset.py	88.44% <ø> (ø)
...datasets/datasets/top_down/topdown_mpii_dataset.py	42.71% <ø> (ø)
...sets/datasets/top_down/topdown_mpii_trb_dataset.py	51.75% <ø> (ø)
mmpose/models/detectors/mesh.py	92.24% <ø> (ø)
mmpose/models/losses/mesh_loss.py	97.65% <ø> (ø)
mmpose/utils/hooks.py	47.05% <47.05%> (ø)
mmpose/apis/inference.py	66.45% <58.82%> (-2.26%)	⬇️
mmpose/deprecated.py	65.38% <65.38%> (ø)
... and 17 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3ef8e6d...5f80a9a. Read the comment docs.

[innerlee]

When we change code in a breaking way, e.g., renaming a class, We need do some thing to help users with migration.

One way to do this is to leave an empty shadow class with the original name at the original path. In its init function, print a message about the rename, and then raise an error.

[jin-s13]

When we change code in a breaking way, e.g., renaming a class, We need do some thing to help users with migration.

One way to do this is to leave an empty shadow class with the original name at the original path. In its init function, print a message about the rename, and then raise an error.

Is it necessary to add this info now? Or is there any elegant way to do so?

[jin-s13]

There are conflicts @liuxin9608 , please resolve them.

[innerlee]

Looks good modulus the above comments.

one comment for future reference:
when there is an unrelated bulk change like the keys=['img'], formatting, the best way is to make a separate pr for that change.
this will make reviews much easier, and that pr will also be merged quicker