feat: Implement error handling and return it to analytics

[mfteloglu]

Motivation

• Check Notion and Linear

• Handle specific errors and inform Analytics about it

• Refer the Analytics PR fix: Sourcing trigger flow errors parma-analytics#54

Changes

• task_id is adapted to /companies endpoint
• New custom errors are defined
• Analytics is informed with /crawling-finished
• task_id and error list is returned via /crawling-finished

Checklist

• added myself as assignee
• correct reviewers
• descriptive PR title using conventional commits.
• description explains the motivation and details of the changes
• tests cover my changes
• my functions are fully typed
• documentation is updated
• CI is green
• breaking changes are discussed with the team and documented in the PR title ! (e.g. feat!: Update endpoint)

[linear]

DS-122 Implement logging and update Notion page

Please implement the logging for at lease one exemplary module, sending the data to the crawling finished endpoint in the Analytics endpoint. Please ping us when you are done so we can apply this for all other modules as well.

Also, please ensure the logging Notion page is up-to-date.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
235	153	65%	0%	🟢

New Files

File	Coverage	Status
parma_mining/github/helper.py	75%	🟢
parma_mining/mining_common/exceptions.py	89%	🟢
TOTAL	82%	🟢

Modified Files

File	Coverage	Status
parma_mining/github/analytics_client.py	45%	🟢
parma_mining/github/api/main.py	66%	🟢
parma_mining/github/client.py	33%	🟢
parma_mining/github/model.py	85%	🟢
TOTAL	57%	🟢

updated for commit: 8be8897 by action🐍

[egekocabas]

I fully tested these changes with the la-famiglia-jst2324/parma-analytics#54 and I had some fixes in analytics PR as well 😅
I am leaving for @Constantin343 's review for the implementation but it is working 👌🏻

[Constantin343]

Looks good! Only one suggestion for refactoring