[O2B-1621] Associate eor reasons to user by user id and not name

[graduta]

I have a JIRA ticket

• branch and/or PR name(s) include(s) JIRA ID
• issue has "Fix version" assigned
• issue "Status" is set to "In review"
• PR labels are selected

Notable changes for users:

• none

Notable changes for developers:

• the run use case(used by the HTTP API) is now throwing error if the change of an EOR reason does not contain valid id of an existing user
• the usecase has been adapted to throw rather than return object with error
• the run service has also been updated but this as it is used by Kafka and gRPC services for automatic EOR purposes, do not require to have a user id
• ticket is needed to achieve easier pseudonymization for Bookkeeping

Changes made to the database:

• table eor_reason now is associated to user tables by user id

[codecov]

Codecov Report

❌ Patch coverage is 79.54545% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 46.24%. Comparing base (8ee4a49) to head (834be32).

Files with missing lines	Patch %	Lines
...261001100000-eor-reasons-last-edited-by-user-id.js	55.55%	4 Missing ⚠️
lib/public/views/Runs/format/editRunEorReasons.js	0.00%	2 Missing ⚠️
lib/public/views/Runs/format/formatRunEorReason.js	0.00%	2 Missing ⚠️
lib/public/views/Runs/Details/RunPatch.js	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2235      +/-   ##
==========================================
+ Coverage   46.23%   46.24%   +0.01%     
==========================================
  Files        1041     1042       +1     
  Lines       17179    17190      +11     
  Branches     3129     3127       -2     
==========================================
+ Hits         7942     7949       +7     
- Misses       9237     9241       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.