Django-esteid

- Add new optional parameter `random_bytes` to all `authenticate` methods. This allows the userland implementation to generate their own random bytes that are used for authentication hash. As a result the userland is able to implement a "two-step" authentication where the verification code is shown to the user first and then after a small delay the notification is sent to their phone.
- For standardization sake, the random_bytes can also be set manually for id-card authenticate call.

- update pyasice to 1.2.0 (and above)

Internal:

- bump some dependency versions

Welcome web-eid

The authentication and signing mechanisms for ID-card now use the modern [web-eid](https://www.id.ee/en/article/web-eid/) platform. This release adds support for signing from the previous 3.4 beta release that allowed for authentication using web-eid and ID-Card.

This is the first testing release using the new [web-eid](https://www.id.ee/en/article/web-eid/) platform. The release currently supports signing documents using the new web-eid extension. Changes to the codebase have been implemented in both the modern signers pattern and also in the legacy actions pattern of using django-esteid.

> Note: The support for authentication with idcard shall be implemented in a separate release soon.

**Changes:**

- esteid-helper bundled under `esteid-new` and `esteid-test` static folders has been removed. Please use the new `esteid-helper` directory instead (or install esteid-helper via npm).
- The files to include are now:
- <static_dir>/esteid-helper/web-eid.js
- <static_dir>/esteid-helper/Esteid.main.web.js
- <static_dir>/esteid-helper/Esteid.main.min.js
- Note: When interfacing with the legacy actions api use `LegacyIdentificationManager` instead of `IdentificationManager`
- Changed: `IdentificationManager.getError` now expects the entire error object as its argument instead of only the error message value. See changes in `esteid/templates/esteid/test-new.html` and `esteid/templates/esteid/test.html` for an example on how to update your code.
- Changed: Django imports now work in a backwards compatible manner to allow usage with old django (on your own risk).

- Changed: Due to the changes in the underlying infrastrucuture the certificate and signature values sent to server during id-card signing are now base64 encoded instead of hex encoded. This should not affect the users of the library unless you are interfacing with the values directly in your own code.

- Add `issuer_country` and `subject_country` to `Certificate` class
- Use `re_path` for urls
- Replace all `ugettext_lazy` calls with `gettext_lazy`
- Use `force_str` instead of the `force_text` which was removed in django 4.0

- Update test matrix:
- Remove python 3.6 and 3.7
- Use latest poetry in CI
- Add python 3.9 and 3.11
- Add django 4.0 and 4.1
- Remove django 2.0

With this release we now allow `action.get_bdoc_container_file` to return a file-like object too. This is mostly a compatibility fix for users of legacy implementations as it is part of the deprecated api. As a result it is easier to use the actions api with remote filesystem backends like S3.

**Also:**

- Use Github actions instead of travis for CI
- Update smartid test identity codes in unit tests
- Add tests for open_container method
- Use poetry for packaging and dependency management