About DCT debugging problems

[yajo]

Hi all. We've been busy refining debugging within DCT-based projects, as you can see in #350.

There are some issues that fell outside of Doodba that affected the debugging experience:

• The recordset's repr() changes and is misleading odoo-ide/pydevd-odoo#1. Fix: Rebuild your image pulling a new base using invoke img-build --pull

• Pydevd-odoo does not work for Python 3.8  odoo-ide/pydevd-odoo#3 + Module with __file__=None is not supported microsoft/debugpy#475. Workaround: Install debugpy from git master, which includes latest patches. Just add this to your pip.txt file:

  # HACK https://github.com/microsoft/debugpy/issues/482
  git+https://github.com/microsoft/debugpy.git
  
  # Add this only for v14
  pydevd-odoo
  

  The real fix will be to revert FIX: Temporarily remove pydevd-odoo #341 for v14, and to upgrade debugpy to the next release once it happens.

• debugpy maps properly the path for setting breakpoints, but not for module location (and thus cannot open the file using the call stack while debugging) microsoft/debugpy#482. Workaround and fix: the same as for the previous bug.

• Debug adapter doesn't send pathMappings to local container microsoft/vscode-python#14820. Fixed in DCT v2.5.0 (workaround applied: Tecnativa/doodba-copier-template@6315685). Fix: update your subproject with copier update.

I hope this lets everybody have a pleasant debug experience inside VSCode while the proper bricks get into their walls.

cc @carlosdauden