[SPIKE] feat: refresh record `count_submitted_responses` column using context functions

[jfcalvo]

Description

This PR include changes to explore the possibility of using a new column named count_submitted_responses to records table.

This new column will be refreshed every time a response is created/updated/deleted maintaining a correct counter value of the submitted responses that a record has.

With this value we can easily filter records that are in completed status, using the distribution strategy for the associated dataset.

Changes that are included in this PR:

• Refresh count_submitted_responses when a response is created/updated/deleted.

Changes that are not present in this PR

• Refresh count_submitted_responses when responses are created in bulk.
• Refresh count_submitted_responses when records are created/upserted in bulk.
• Refresh modified records into the search engine.
• Include count_submitted_responses into the search engine mapping.
• Add new calculated value status to record responses.
  • We need to explore if this could fit into the ORM model or Pydantic schemas.
• Modify the search endpoint to return records with specific status value.

Refs #5069

Type of change

(Please delete options that are not relevant. Remember to title the PR according to the type of change)

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Refactor (change restructuring the codebase without changing functionality)
• [ ] Improvement (change adding some improvement to an existing functionality)
• [ ] Documentation update

How Has This Been Tested

(Please describe the tests that you ran to verify your changes. And ideally, reference tests)

• [ ] Test A
• [ ] Test B

Checklist

• [ ] I added relevant documentation
• [ ] follows the style guidelines of this project
• [ ] I did a self-review of my code
• [ ] I made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I filled out the contributor form (see text above)
• [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.99%. Comparing base (b23f3d8) to head (5adc94b).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## feat/update-datasets-distribution #5106 +/- ## ===================================================================== + Coverage 91.98% 91.99% +0.01% ===================================================================== Files 136 136 Lines 5850 5860 +10 ===================================================================== + Hits 5381 5391 +10 Misses 469 469 ``` | [Flag](https://app.codecov.io/gh/argilla-io/argilla/pull/5106/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=argilla-io) | Coverage Δ | | |---|---|---| | [argilla-server](https://app.codecov.io/gh/argilla-io/argilla/pull/5106/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=argilla-io) | `91.99% <100.00%> (+0.01%)` | :arrow_up: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=argilla-io#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.