ci: add debianize build pipeline

[yedpodtrzitko]

add Debian package build into pipeline

This was quite a bamboozle as the Debian building somehow feels like it does not behave deterministically - one day it is working certain way and when I pick it up the next day where I left it, it behaves differently.
Specifically - one day it was pinning the exact version of Debian dependencies. The next day it was not pinning them, and I couldnt reproduce the previous behaviour again. This made it easier for installation, but also it requires to:

• add manually pinned b2sdk dependency into debian/control as the latest available version of b2sdk Debian package is incompatible: (ImportError: cannot import name 'UploadMode' from 'b2sdk.v2' which was added later
• which also means we need an up-to-date Debian package of b2sdk, see ci: add debian build pipeline b2-sdk-python#287

tl;dr - package build is working and it's uploaded into B2 bucket:

• https://f005.backblazeb2.com/file/reef-b2-debian/python3-b2sdk_1.21.0-1_all.deb

• https://f005.backblazeb2.com/file/reef-b2-debian/backblaze-b2_3.9.0-1_all.deb

Repo Setup

• add the following pair of secrets for uploading the package into B2 bucket:

  • B2_DEBIAN_APPLICATION_KEY_ID
  • B2_DEBIAN_APPLICATION_KEY

• add the following environment variable to determine which B2 bucket upload will go to:

  • B2_DEBIAN_BUCKET_UPLOAD

[mpnowacki-reef]

let's skip this step if vars are missing

[mpnowacki-reef]

debian is probably decades away from supporting this python, I assume that's not a problem? like maybe some things here pass even though they are syntax errors in the version that debian is gonna use?

[yedpodtrzitko]

3.11 is actually the default version in the latest Debian.

But we run testsuite for all the supported Python versions (3.7+), so if anything would be misbehaving we'd find out there, no?