CI Strategy EOY 2020

[Travis-CI](https://travis-ci.com/github/hardbyte/python-can) has been slow of late, although this _might_ improve now we have migrated to travis-ci.com

In #591 I suggested we add support for arm by using Shippable. In #705 @karlding added arm64 support using travis-ci.
In #661 @karlding proposed moving to Azure Pipelines.
In #940 @felixdivo proposed:
> - retain all Github workflow tests, which test with CPython on Linux, macOS and Windows
> - Move CPython 3.10-dev & nightly from Travis to Github workflow
> - remove Travis CI testing except: pypy3 and socketcan tests
> - retain the other Travis jobs like the linter and publishing (for now at least, we can consider moving them in another PR)
> - remove AppVeyor testing as it is entirely covered by Github workflows (right?)

先閱讀 #591、#705、#661 和 #940 中的提案，然後檢查目前的 Travis CI、GitHub workflow 和 AppVeyor 設定。確定哪些 CI 服務和測試工作應予保留或移轉，並且只有在專案形成了經一致同意的策略及相應的移轉範圍後，才視為工作完成。

由索引模型根據 Issue 內容生成。