Maven scope in dependencyManagement

Currently the `commons-io` library is declared with a test scope in the `azure-parent` pom : https://github.com/Azure/azure-libraries-for-java/blob/master/pom.xml#L118

This just caused a rather hard to debug issue for one of my projects where another library used had `commons-io` as a compile dependency (not explicitly set at compile because it is the default), and importing the `azure-parent` "excluded" it, causing my project to fail at runtime.

Quick search shows it may not be a good idea to have scopes in ``, at least not "test" ([first answer I found on SO](https://stackoverflow.com/a/20750041)).

Would it be fair to remove the test scope from `` in `azure-parent`? I can provide the PR.

Apri pom.xml intorno alla riga 118 e ispeziona la dichiarazione di commons-io sotto dependencyManagement. Conferma che lo scope test sia stato rimosso e verifica che il parent non sovrascriva più commons-io come dipendenza di test.

Scritto dal modello di indicizzazione a partire dal testo della issue.