Adding rearrange_pick_dataset_v1

[vincentpierre]

Motivation and Context

Adding a v1 of the data set for the pick task using the new data generator schema.

How Has This Been Tested

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have completed my CLA (see CONTRIBUTING)
• I have added tests to cover my changes.
• All new and existing tests passed.

[aclegg3]

Instead of adding a new entry, you should just replace the links and bump the version on the existing entry. The downloader will handle the versioning for users.

[ASzot]

After we bump the version then the tests on Habitat Lab will fail though @aclegg3. How do we resolve this dependency? We need the new dataset for the tests here to pass: facebookresearch/habitat-lab#774.

[aclegg3]

After we bump the version then the tests on Habitat Lab will fail though @aclegg3. How do we resolve this dependency? We need the new dataset for the tests here to pass: facebookresearch/habitat-lab#774.

I see, this new version doesn't support the current testing scenario in main.

One option would be to leave this PR un-merged and edit the CI config in that Habitat-lab branch to grab this PR for the data download step before pulling and installing main. When we are ready to merge that PR, we'll also merge this and remove that extra step.

[vincentpierre]

I think we want the data to be on a different path than the previous version. I start to think it would be better to have 2 different entries for these 2 datasets (like in the last commit)

[aclegg3]

I understand the reasoning here. We'll add a new entry now to support testing on existing main and the dev branch. Once everything is merged and it becomes irrelevant, we can remove the old entry.