Refactor feedback-callback and update package dependencies

[tieneupin]

Refactored feedback_callback blocks
Migrated the following logic blocks into their own workflows modules, and added unit tests for them:

• atlas_update
• data_collection
• data_collection_group
• processing_job

These workflows will potentially be shared between multiple data processing pipelines (SPA, tomo, and potentially CLEM), so suggestions on where to put them would be much appreciated.

Modified feedback_callback entry points to return dictionary instead of boolean
Some feedback callback functions will request for a message requeue, which our current setup doesn't support. By switching the workflows to return a dictionary, we can add a key to control whether the message gets requeued or not.

Updated project package dependencies
Some package dependencies were also updated:

• Removed the version lock on stomp-py from when 8.1.1 caused us issues
• Removed the FastAPI version lock from when there were conflicting httpx version dependencies
• Added graypy as an explicit package dependency, since we use it directly
• Removed backports.entry_points_selectable now that Python 3.9 has been dropped

[codecov]

Codecov Report

❌ Patch coverage is 74.30168% with 46 lines in your changes missing coverage. Please review.
✅ Project coverage is 36.94%. Comparing base (443fec9) to head (bbf6956).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #688      +/-   ##
==========================================
+ Coverage   35.77%   36.94%   +1.17%     
==========================================
  Files          92       97       +5     
  Lines       11308    11459     +151     
  Branches     1495     1510      +15     
==========================================
+ Hits         4045     4234     +189     
+ Misses       7130     7063      -67     
- Partials      133      162      +29     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[stephen-riggs]

Thanks for doing this, it looks fine to me. As long as you've checked that it ran on the test setup ok then I'm happy for this to go in