Run pydevd tests on github actions. Fixes microsoft#471

src/debugpy/_vendored/pydevd/MANIFEST.in

@@ -1,4 +1,4 @@
-include *.rst *.txt *.md LICENSE .travis.yml appveyor.yml *.pyx *.cpp *.hpp
+include *.rst *.txt *.md LICENSE *.pyx *.cpp *.hpp
 recursive-include pydevd_attach_to_process *.py *.dll *.so *.dylib *.txt *.c *.h *.bat Makefile *.sh *.pyx *.cpp *.hpp
 recursive-include pydevd_attach_to_process/common *.py *.dll *.so *.dylib *.txt *.c *.h *.bat Makefile *.sh *.pyx *.cpp *.hpp
 recursive-include pydevd_attach_to_process/linux_and_mac *.py *.dll *.so *.dylib *.txt *.c *.h *.bat Makefile *.sh *.pyx *.cpp *.hpp

src/debugpy/_vendored/pydevd/README.rst

@@ -1,19 +1,20 @@
 PyDev.Debugger
 ==============
 
-The sources for the PyDev.Debugger (used in PyDev & PyCharm) may be seen at:
+The sources for the PyDev.Debugger may be seen at:
 
 https://github.com/fabioz/PyDev.Debugger
 
 In general, the debugger backend should **NOT** be installed separately if you're using an IDE which already
-bundles it (such as PyDev or PyCharm).
+bundles it (such as PyDev, PyCharm or bundled through debugpy, which is the debug adapter used in 
+VSCode Python and Visual Studio Python).
 
 It is however available in PyPi so that it can be installed for doing remote debugging with `pip` -- so, when
 debugging a process which runs in another machine, it's possible to `pip install pydevd` and in the code use
 `pydevd.settrace(host='10.1.1.1')` to connect the debugger backend to the debugger UI running in the IDE
 (whereas previously the sources had to be manually copied from the IDE installation).
 
-It should be compatible with Python 2.6 onwards (as well as Jython 2.7, IronPython and PyPy -- and
+It should be compatible with Python 2.7 onwards (as well as Jython 2.7, IronPython and PyPy -- and
 any other variant which properly supports the Python structure for debuggers -- i.e.: sys.settrace/threading.settrace).
 
 Recent versions contain speedup modules using Cython, which are generated with a few changes in the regular files
@@ -27,17 +28,10 @@ To generate a distribution to upload to PyPi, `python setup.py sdist bdist_wheel
 which should have a wheel and afterwards `twine upload -s dist/pydevd-*` should be run to actually upload the contents
 to PyPi.
 
-Travis (Linux CI):
+GitHub Actions (CI):
 
-.. |travis| image:: https://travis-ci.org/fabioz/PyDev.Debugger.png
-  :target: https://travis-ci.org/fabioz/PyDev.Debugger
+.. |github_actions| https://github.com/fabioz/PyDev.Debugger/workflows/PyDev.Debugger Tests/badge.svg
+  :target: https://github.com/fabioz/PyDev.Debugger/workflows/PyDev.Debugger Tests/badge.svg
 
-|travis|
-
-Appveyor (Windows CI):
-
-.. |appveyor| image:: https://ci.appveyor.com/api/projects/status/j6vjq687brbk20ux?svg=true
-  :target: https://ci.appveyor.com/project/fabioz/pydev-debugger
-
-|appveyor|
+|github_actions|