GC-47: Add support for Python 3.13:

- Simplify the option presence checks in functional tests to avoid
having to deal with differences in output between Python 3.13 and
older versions (similar checks are already in place for things like
key specification anyway). For more details, see this commit:

https://github.com/python/cpython/commit/c4a2e8a2c5188c3288d57b80852e92c83f46f6f3

GC-48: Update the test framework:

- Slight change required for handling differences in how the output
lines are being broken up during testing.

GC-50: Drop brackets from Vagrant virtualenv prompt:

- Newer versions of virtualenv automatically add brackets and spacing.

GC-50: Fix testing on Vagrant machine:

- Some archives that were previously in use by Debian 11 Bullseye are
now gone, resulting in errors during provisioning. Switch to Debian
12 Bookworm instead.
- Increase amount of memory allocated to test machine - default is
not enough.
- Increase the number of CPUs allocated to test machine to speed-up
compilation times.

GC-44: Added support for Python 3.12:

- Updated documentation.
- Updated release notes.
- Updated supported Python versions in package configuration file.
- Updated Python versions used for tests.

GC-43: Fix Python 3.11 failing CLI test due to subparser masking:

- Renamed the subparser commands to be fully distinct.
- The subparser registration is never reset since the Python test file
is run as part of a single process, thus the two tests would
register two subparsers under the same subcommand.
- In older versions of Python this was not a problem, but with newer
verions (3.11+) this inconsistency has been fixed. For more details,
see:

https://bugs.python.org/issue39716

GC-43: Fix provisioning script for Vagrant machine:

- Version patch number can be longer than one digit, make sure to
strip it correctly.

GC-43: Added support for Python 3.11:

- Updated documentation.
- Updated release notes.
- Updated supported Python versions in package configuration file.
- Updated Python versions used for tests.

GC-42: Added support for Python 3.10:

- Updated documentation.
- Updated release notes.
- Updated functional tests (small tweak for help output change).
- Added signing key for the Python 3.10 and 3.11 releases.
- Updated supported Python versions in package configuration file.
- Updated Python versions used for tests.

GC-45: Update copyright information:

- Changes to code base were previously done in 2020 as well (based on
git history).

GC-45: Fix deprecation warning for elliptic curve key generation:

- Passed-in curve parameter must be an object instance, not a class.

GC-45: Use non-naive datetime objects that include timezone:

- Newer versions of cryptography prefer/insists on use of UTC-based
datetime objects with correctly set timezone.

GC-45: Upgrade to cryptographyt version 42.0:

- Passing in backend is no longer required/possible.

GC-45: Replace freezegun with time-machine for data/time-related tests:

- The freezegun is no longer maintained, and it also does not handle
timezones that well.
- The time-machine project seems to be actively maintained, and
provides the same functionality.

GC-45: Update development-related requirements:

- Dropped ability to run setup.py test command (deprecation).
- Updated documentation for tox invocations.
- Updated all test and development-related requirements.
- Dropped use of deprecated project pytest-runner.
- Updated tox configuration (deprecations).
- Unfortunately, tox seems to mess with the COLUMNS environment
variable that breaks functional tests which depend on specific
formatting of help (breaklines included). Make sure the tests run
with column width of 80.

GC-45: Fix/update documentation building:

- Updated Sphinx requirement to latest version compatible with Python
3.8.
- Updated Sphinx configuration file to match with configuration
generated by the updated version.
- Updated copyright notices in changed files.

GC-45: Drop support for Python 3.5, 3.6, and 3.7:

- Updated documentation, removing references to versions as being
supported.
- Switched the Vagrant test machine to Debian Bullseye (still in LTS
support) to match the main development environment.
- Updated functional tests for output changes in OpenSSL CLI from
Debian Bullseye.
- Updated Tox configuration and instructions.
- Dropped workaround for Python 3.5.
- Updated package requirements.
- Updated release notes.

GC-39: Added support for Python 3.9:

- Updated release notes
- Updated functional test for changes in help output in Python 3.9.
- Updated comments on public signing keys used for validating the
Python archives when using Vagrant provisioning.
- Updated supported Python versions in package configuration file.
- Updated Python versions used for tests.

GC-37: The --csr and --key-specification options should be exclusive:

- Updated list of invalid invocations in the unit tests.
- Updated parsers for server and client subcommands.

GC-37: Deduplicate additional tests for validation of CLI arguments:

- Merge the tests for invoking commands without mandatory positional
arguments into test for invalid CLI invocations.
- Merge the tests for invoking renew commands with conflicting
positional arguments into test for invalid CLI invocations.

GC-37: Include ECDSA when testing that commands use correct key specification:

- Updated tests for server, client, and renew commands.
- Parametrised the tests so they can cover different sizes of RSA
keys, as well as different elliptic curve algorithms.

GC-37: Deduplicate option presence testing from functional tests for ECDSA key specifications:

- Updated the functional tests that cover ECDSA key specifications.
- Dropped tests for option presence since those tests already exist in
a dedicated functional test.
- Dropped testing of invalid invocations - those are better off
covered with unit tests already.
- Reworded the tests so they make more sense.

GC-37: Deduplicate option presence testing from functional tests for RSA key specifications:

- Updated the functional tests that cover RSA key specifications.
- Dropped tests for option presence since those tests already exist in
a dedicated functional test.
- Dropped testing of invalid invocations - those are better off
covered with unit tests already.
- Reworded the tests so they make more sense.

GC-37: Use KeyGenerator instead of generate_private_key in unit tests:

- Replaced all uses of generate_private_key with KeyGenerator
invocations that explicitly request 2048-bit RSA.

GC-37: Update status command to include relevant/correct information about ECDSA algorithms:

- Updated functional test to include case where CA hierarchy has been
initialised with the ECDSA keys.
- Updated unit tests to include testing of output for entities that
use ECDSA keys.
- Use the key_specification_from_public_key function to obtain
information about key in use (instead of assuming it's RSA).

GC-37: Implement renewals with new private keys for ECDSA when previous certificate was issued using CSR:

- Added functional test that covers the scenario.
- Parametrise the unit test used to verify that new key generation
follows the same key specification.
- Update test for checking if new private key gets generated to use
key specification instead of key size.

GC-37: Added functional tests for using ECDSA CSRs:

Tests are passing out-of-the box, no changes were required for the
ones added.

GC-37: Added ECDSA support for issuing client certificates via client command:

- Added functional test.
- Updated unit tests.
- Expose ECDSA key specification in the client command help.

GC-37: Added ECDSA support for issuing server certificates via server command:

- Added functional test.
- Added unit tests.
- Updated existing functional test that checks for avertising of curve
support for key specification in the init command to be a bit less
fragile in case the output gets broken-up into different lines in a
slightly different location.
- Implement ability to get public key specification out of ECDSA
public key.
- Expose ECDSA key specification in the server command.
- Updated inline documentation.

GC-37: Refactor functional tests or renew command key specification handling:

- Generate the custom private keys at top of the test.
- Updated wording.
- Rename the function to explicitly reference RSA to be consistent
with the remaining tests.

GC-37: Refactor functional tests for client command key specification handling:

- Use separate test for checking use of CA hierarchy default key
specification.
- Use separate test for checking use of --key-specification option.
- Do not check public key size in certificate - this is not relevant
for this particular functional test, and there are already unit
tests that verify correct public key is used.

GC-37: Refactor functional tests for server command key specification handling:

- Use separate test for checking use of CA hierarchy default key
specification.
- Use separate test for checking use of --key-specification option.
- Do not check public key size in certificate - this is not relevant
for this particular functional test, and there are already unit
tests that verify correct public key is used.

GC-37: Added ECDSA support for initialising CA hierarchy:

- Added functional test.
- Added unit tests.
- Updated key specification parsing to support ECDSA specification
using curve name.
- Updated KeyGenerator to handle ECDSA private keys generation.
- Updated inline documentation.

GC-37: Added support for showing key algorithms to the status command:

- Updated functional test for the status command to include a variety
of key algorithms and to test for their representation in the
output.
- Added unit tests.
- Updated the status command to extract key algorithm information from
the issued certificates and output the information.

GC-37: Added support for requesting custom RSA key size when renewing:

- Added functional test.
- Added unit tests.
- Updated existing functional test for renew command help to cope with
addition of one more option (output lines from help changed).
- Added new CLI option for passing-in key specification, used in
combination with the --new-private-key option.
- Renew command function now accepts key specification
parameter. Updated existing code and tests accordingly for the new
function signature.
- If key specification is not passed-in and new private key is
requested, key size is extracted from existing artefacts (e.g. it
does not use CA hierarchy's key size).

GC-37: Added support for requesting custom RSA key size when issuing client certificates:

- Added functional test.
- Added unit tests.
- Added new CLI option to the client command.
- Updated the client command to use the passed-in key specification.
- Updated existing tests to cope with changes to the client command
function signature.
- Fixed small typo in docstring for the server command.
- Fixed functional test for client command help that expected
positional argument in a specific line.

GC-37: Added support for requesting custom RSA key size when issuing server certificates:

- Added functional test.
- Added unit tests.
- Added new CLI option to the server command.
- Updated the server command to use the passed-in key specification.
- Updated existing tests to cope with changes to the server command
function signature.

GC-37: Rename the test for server key specification:

- The test should be able to cover all of the server command-related
key specification functionality.

GC-37: Refactor key specification handling:

- Perform the key specification parsing within CLI module itself,
don't do it via crypto module.
- Pass-in tuple consisting out of algorithm and associated parameters
into the init command instead of key generator.
- Updated all tests to accomodate the change in init function
signature.
- Simplify the KeyGenerator class.
- Do not test if KeyGenerator class sets the properties via
constructor - it is sufficient to test string represenation and key
generation.

GC-37: Added support for requesting custom RSA key size when initialising the CA hierarchy:

- Added functional test.
- Added unit tests.
- Added new CLI option for specifying the algorithm.
- Implemented KeyGenerator factory-like class that can be called to
generate a private key with desired specification.
- The init init function now accepts a callable that is used to
generate private keys.
- The generate_ca_hierarchy function now accepts a callable that is
used to generate private keys.
- Updated existing unit tests to cope with changes to the init
and generate_ca_hierarchy function signatures.
- Updated existing unit tests to cope with changes to existing
functionality.
- Updated existing functional tests to cope with changes in command
output.

GC-37: Introduce gctmpdir fixture for reducing duplication in tests:

- Fixture can be used to initialise the temporary directory with
1-level deep Gimmecert hierarchy. It is very useful for tests that
do not care about hierarchy details, while at the same time being
much faster than the sample directory one.
- Fixture should not be used for testing of init/status
commands (since those heavily test what the hierarchy looks like).

GC-33: Added support for Python 3.8:

- Updated release notes.
- Updated documentation.
- Updated Python versions used for tests.
- Updated supported Python versions in package configuration file.

GC-35: Drop support for Python 3.4:

- Updated documentation, removing Python 3.4 as supported version.
- Updated documentation to include support for Python 3.7 (this was
already supported, but documentation did not list it in a couple of
places).
- Updated Tox configuration with list of supported Python
versions.
- Build Python 3.5.x for full test against all Python versions in
order to make it independent of underlying distribution Python
version.
- Update package requirements.
- Updated release notes.

GC-35: Freeze time when testing status command outputs:

Freezing the time will ensure the tests can be run in future without
having to make modifications for issuance dates - otherwise the tests
will fail because certificates will be reported as expired.

Noticket: Fix the release script confirmation verification:

- Conditional for verifying user's request to publish the release was
missing.

Noticket: Fix the release script confirmation verification:

- Conditional for verifying user's request to publish the release was
missing.