Adding auto-ts from PyPI

[sugatoray]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/auto-ts) and found some lint.

Here's what I've got...

For recipes/auto-ts:

• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/auto-ts) and found it was in an excellent condition.

[sugatoray]

PR is ready. Request for review/merging.

cc: @conda-forge/help-python @xhochy

[sugatoray]

Note for Reviewer(s)

I have made the following temporary changes to make the build pass.

• Added temporary work-around steps to create the requirements.txt file dynamically.
• Added LICENSE file from the GitHub repository.

However, a proper fix in the upstream repo is a desirable longterm solution. With that in mind, I have opened up the following issue:

• Add requirements.txt and LICENSE file to tar.gz source on PyPI AutoViML/Auto_TS#112

And, also pushed the intended fix via the following PR:

• Update packaging: add MANIFEST.in and py.typed AutoViML/Auto_TS#111

cc: @AutoViML