ordered-uploading

[tonylampada]

Description

The upload image endpoint has input parameters sequence_order and sequence_size that allows the client to control the parameter used to sort images in the backend.

This PR:

• Exposes that as new parameters in project.single_upload method
• Automatically uses that in workspace.upload_dataset so that files are saved in the alphanumerical order they are found in the filesystem (instead of a random order).

So now if you run $ roboflow import path/to/dataset/

you get something like this:

Type of change

Please delete options that are not relevant.

• [x] New feature (non-breaking change which adds functionality)

How has this change been tested, please provide a testcase or example of how you tested the change?

Tested by uploading it to staging from roboflow-python dev environment

Any specific deployment considerations

Will release version 1.1.18

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: tonylampada
:x: pre-commit-ci[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}