fix(treesitter): highlight of imported names in python

Problem:  module names in python import statements are (now) highlighted
          with `@module`, and `@module` has the same highlight as
          keywords (such as `import`).

Cause:    nvim-treesitter update which modifies python's highlight
          query.

Solution: don't highlight `@module.python`. In the future, we may want
          to make `@module` un-highlighted by default instead, since it
          seems that only a few languages need it.

Fixes: #371

Author: tmillr

CHANGELOG.md

@@ -16,6 +16,7 @@ The format is based on [Keep a Changelog], and this project adheres to [Semantic
 
 -  Fixed JSX/TSX tags are missing highlights with nvim 0.10 (#360)
 -  Fixed loading palette or spec before colorscheme disrupts colors (#362 fixed-by #363)
+-  Fixed incorrect highlight of name/binding in python import statements (#371)
 
 ## [v1.1.2] - 05 August 2024
 

lua/github-theme/group/modules/treesitter.lua

@@ -301,6 +301,7 @@ If you want to stay on nvim 0.7, disable the module, or track on 'v0.0.x' branch
     ['@type.builtin.python']                    = { link = '@constant' },
  -- ['@type.python']                            = { link = '@function' },
     ['@variable.builtin.python']                = { link = '@constant' },
+    ['@module.python']                          = FALLBACK_OR_NONE,
 
     -- Ruby
     ['@label.ruby']                             = { fg = syn.const },