{Packaging} Remove azure-devtools as a dependency

[fengzhou-msft]

Description

MSI package building failed in CI caused by building the latest yarl and multidict packages from source. Details in below comment.

These 2 packages are implicitly downloaded as they are in the dependency tree of azure-devtools. azure-devtools is only needed for development and testing and should be removed as a dependency in requirements.txt for building azure-cli packages. The setup.py for azure-cli does not contain azure-devtools.

yarl is used in storage-blob-preview, but the code has workaround when yarl is not available. So it's OK to remove it. Besides, if users install through pip install azure-cli, yarl is not installed either and we haven't received relative issues.

Testing Guide

Packages tested in build_test branch: https://dev.azure.com/azure-sdk/public/_build/results?buildId=573646&view=results

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

[yonzhan]

Packaging

[jiasli]

Any reason why pinning these 2 dependencies fixes the issue?

[jiasli]

When using yarl==1.6.0, pip is downloading yarl-1.6.0-cp36-cp36m-win32.whl (link), but now it seems yarl has dropped win32 support.

Azure CLI is still using a 32-bit Python:

azure-cli/build_scripts/windows/scripts/build.cmd

Line 15 in 3de6396

set PYTHON_DOWNLOAD_URL="https://azurecliprod.blob.core.windows.net/util/Python368-32.zip"

Without the win32 wheel, pip will download source code yarl-1.6.2.tar.gz (link) and build a wheel which requires Python.h (link) which doesn't exist in https://azurecliprod.blob.core.windows.net/util/Python368-32.zip.

The same happens for multidict.