chore: add colour to the advisory generation output. (#109)

I find the output from the Advisory generation to be an unreadable wall
of text.

This adds a scattering of colour to the notices for SAs that have had an
action applied to them.

This is manage through the addition of
[Colorama](https://pypi.org/project/colorama/). I selected this one as
it manages the colours and styles while taking into account the platform
it's run on, is actively maintained, and has been around for more than a
decade.

<img width="1125" height="1072" alt="image"
src="https://github.com/user-attachments/assets/90966c1a-3884-448a-b302-f831648b2e3c"
/>

I note that the `poetry.lock` has an unexpected removal. Could this be
because it is included via the new Colourama?

Author: Unifex

poetry.lock

@@ -3,6 +3,7 @@ name = "drupal-advisory-database"
 requires-python = ">= 3.13"
 
 [tool.poetry.dependencies]
+colorama = "^0.4.6"
 jsonschema = "^4.23.0"
 markdownify = "^1.1.0"
 mypy = "^1.15.0"
@@ -12,6 +13,7 @@ ruff = "~0.14.0"
 semver = "^3.0.4"
 types-jsonschema = "^4.23.0.20241208"
 types-requests = "^2.32.0.20250328"
+types-colorama = "^0.4.15.20240311"
 
 [tool.poetry]
 package-mode = false

pyproject.toml

@@ -16,6 +16,7 @@
 
 import requests
 import semver
+from helpers import text_is
 from markdownify import markdownify
 
 from typings import drupal, osv
@@ -350,10 +351,13 @@ def patch_advisory(sa_id: str, sa_advisory: drupal.Advisory) -> bool:
 
     if before == sa_advisory['field_affected_versions']:
       sa_advisory['field_affected_versions'] = after
-      print('  \\- patched affected versions')
+      print('  \\- ' + text_is.success('patched affected versions'))
       return True
     print(
-      f'  \\- skipped patching as affected version is now "{sa_advisory["field_affected_versions"]}"'
+      '  \\- '
+      + text_is.warning(
+        f'skipped patching as affected version is now "{sa_advisory["field_affected_versions"]}"'
+      )
     )
   return False
 
@@ -375,14 +379,14 @@ def build_osv_advisory(
   # we expect that the downloader has excluded PSA type entries, but
   # we still guard against them here just in case one slips through
   if sa_advisory['field_is_psa'] == '1':
-    print(' \\- skipping as it is a psa? (this should not happen)')
+    print(' \\-' + text_is.error('skipping as it is a psa? (this should not happen)'))
     return None
 
   # there's not really much we can do if there isn't an affected version
   # todo: since build_affected_ranges throws if this isn't present, it might
   #  make more sense to use that, with a custom exception class
   if sa_advisory['field_affected_versions'] is None:
-    print(' \\- skipping as we do not have any affected versions')
+    print(' \\- ' + text_is.notice('skipping as we do not have any affected versions'))
     return None
 
   osv_advisory: osv.Vulnerability = {
@@ -461,7 +465,10 @@ def generate_osv_advisories() -> None:
       os.makedirs(f'advisories/{name}', exist_ok=True)
       if is_existing_advisory_ahead(name, sa_id, osv_advisory['modified']):
         print(
-          ' \\- error: current modified date is ahead of the proposed modified date (is your cache up to date?)'
+          ' \\- '
+          + text_is.error(
+            'error: current modified date is ahead of the proposed modified date (is your cache up to date?)'
+          )
         )
         exit(1)
 

scripts/generate_osv_advisories.py

@@ -0,0 +1,19 @@
+from colorama import Fore, Style, just_fix_windows_console
+
+just_fix_windows_console()
+
+
+def notice(message: str) -> str:
+  return f'{Fore.YELLOW}{Style.DIM}{message}{Style.RESET_ALL}'
+
+
+def success(message: str) -> str:
+  return f'{Fore.GREEN}{message}{Style.RESET_ALL}'
+
+
+def warning(message: str) -> str:
+  return f'{Fore.YELLOW}{message}{Style.RESET_ALL}'
+
+
+def error(message: str) -> str:
+  return f'{Fore.RED}{message}{Style.RESET_ALL}'