[FEATURE-BRANCH] feat: add support for value zero on rating questions

[jfcalvo]

Description

This PR is the feature branch with all the changes to support zero value on rating questions.

Closes #4822

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)
• [x] 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)

• [x] Adding and changing tests.

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/)

Argilla Community Growers

Thanks for your contribution! As part of our Community Growers initiative 🌱, we're donating Justdiggit bunds in your name to reforest sub-Saharan Africa. To claim your Community Growers certificate, please contact David Berenstein in our Slack community or fill in this form https://tally.so/r/n9XrxK once your PR has been merged.

Pull Request Templates

Please go the the Preview tab and select the appropriate sub-template:

• 🐞-bug
• 📚-documentation
• 🆕-features

Generic Pull Request Template

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Closes #<issue_number>

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/)