CI: Move last builds from Travis to Azure
I think this makes sense, and it will simplify things having a single CI system.

If I'm not missing anything, there are few challenges:
- The number of jobs (I think we should get 10 extra concurrent jobs in Azure, since the CI is ok but will be too slow)
- Setting up databases in Azure (I think we currently set up Postgres and MySQL, and may be in the future we want SQL server too #9097)
- I think we have some encrypted stuff in azure for GBQ (probably can be easily moved to Azure secrets)

If there is any objection, let me know, otherwise I'll move forward with this.

CC: @bhavaniravi 