New events, copilot user, and agent support for python 3

[Leo-Send]

This is a rebase of my previous PR onto the python3-version branch.

[Copilot]

Pull request overview

This PR rebases prior work onto the python3-version branch and extends the issue/bot/author pipelines to better support new GitHub event types (incl. Copilot), agent classification, and additional cross-issue connection handling.

Changes:

• Extend GitHub issue event processing with Copilot-specific handling, connected-event reconstruction, and additional event metadata (e.g., merge commit hash, commit author for commit_added).
• Introduce shared GitHub/Copilot user utilities (github_user_utils) and integrate them into bot processing and author postprocessing (incl. optional Copilot user unification).
• Update both GitHub and JIRA issue processing to normalize issue types (e.g., “New Feature” → “Feature”) and adjust in-place processing patterns (stop relying on returned mutated lists).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
issue_processing/jira_issue_processing.py	Normalizes JIRA issue types and adjusts user-data insertion/state event generation.
issue_processing/issue_processing.py	Adds Copilot/connection reconstruction logic, extends event metadata, and updates user syncing/output fields.
github_user_utils/github_user_utils.py	New shared constants/helpers for GitHub/Copilot user and bot/agent name handling.
github_user_utils/init.py	Initializes the new github_user_utils package.
bot_processing/bot_processing.py	Adds agent list support and Copilot-agent handling; improves bot-name variant matching.
author_postprocessing/author_postprocessing.py	Adds Copilot unification option and extends “GitHub noreply” replacement logic to cover Copilot and commit_added info.

Comments suppressed due to low confidence (1)

author_postprocessing/author_postprocessing.py:116

• Inside fix_github_browser_commits(), author_data_new is only defined when authors.list exists in the current directory. If issues-github.list is encountered without authors.list (e.g., partial outputs), this will raise UnboundLocalError when building author_name_to_data. Initializing author_data_new per directory avoids that failure mode.

    # Check for all files in the result directory of the project whether they need to be adjusted
    for filepath, _, filenames in walk(data_path):

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Leo-Send]

I fixed the relevant suggestions. This PR should be ready to be tested now.

[bockthom]

@Leo-Send Thanks for creating this pull-request. As I ran all python3 scripts of this repo, I had to fix a view missing imports in all files, and there was also one encoding problem that I had to fix. Therefore, I pushed two commits to your branch that contain these fixes. (So please pull before you continue working on this.)

There is one little issue remaining where I need your help:

username.list Does not contain the right name any more. Here is the diff - an example of a singe username:

Python2:
"zzy19970428";"zzy19970428";"could.not.resolve@a66tdd22mt"
Python3:
"zzy19970428";"None";"could.not.resolve@dfrfg3s1ti"

So the difference is: If there is no name, in python2, the username was used as name, and a random e-mail address was created. However, in python3, if there is no name, the name becomes the string "None", and suddenly all users are merged in the database because they all share the name "None". @Leo-Send Could you please figure out where this breakes? The usernames list should be created in issue_processing.py (and it might be also updated in bots_processing.py). If we don't have a name, we should use the username as name, not None.

Thank you!

Everything else of the python3 version works well - I did not spot any differences in the outcomes compared to the python2 version except for this username problem.