chore: add the version of python-gitlab to GitlabError

[JohnVillalovos]

People will post tracebacks of exceptions but not post information on
the version of python-gitlab used.

Add the version of python-gitlab to the GitlabError exception message.

[nejch]

Thanks @JohnVillalovos! This is a specific implementation for one exception. If we do this, a more generic approach might be useful I think, otherwise we might have to litter our code with custom exception messages.

But I'm also not sure if exception messages are the right place for this. Did you get this idea from existing libraries? I think we should look into #2080, maybe in combination with exception hooks if we want this 🤔 not sure, it just seems more like a logging topic IMO?

[JohnVillalovos]

Good idea. Let me explore having it in the base GitlabExeception class. But probably not today...

[codecov-commenter]

Codecov Report

Merging #2093 (7577c91) into main (f9b7c7b) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #2093   +/-   ##
=======================================
  Coverage   94.72%   94.73%           
=======================================
  Files          78       78           
  Lines        5083     5088    +5     
=======================================
+ Hits         4815     4820    +5     
  Misses        268      268           

Flag	Coverage Δ
cli_func_v4	82.42% <80.00%> (-0.01%)	⬇️
py_func_v4	81.19% <100.00%> (+0.01%)	⬆️
unit	85.84% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
gitlab/exceptions.py	100.00% <100.00%> (ø)

[nejch]

Good idea. Let me explore having it in the base GitlabExeception class. But probably not today...

I would also look at https://stackoverflow.com/questions/5191830/how-do-i-log-a-python-error-with-debug-information as a clean option. Of course, we'd need a nicer setup for #2080 first.