Fix "isReady" method on inject

[RomuDeuxfois]

Proposed changes

• Fix is ready method on inject
  • mandatory
  • mandatory group
  • mandatory on condition
• Add tests
• Fix i18n thanks to WWT feedbacks

Linked to:

• Fix "isReady" method on inject #3336
• [nuclei/nmap] Improve & fix contracts injectors#78

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Project coverage is 44.31%. Comparing base (7bee250) to head (d4274a1).
Report is 5 commits behind head on release/current.

Files with missing lines	Patch %	Lines
.../io/openbas/injectors/caldera/CalderaContract.java	0.00%	1 Missing ⚠️

Additional details and impacted files

@@                  Coverage Diff                  @@
##             release/current    #3336      +/-   ##
=====================================================
+ Coverage              44.23%   44.31%   +0.07%     
- Complexity              2633     2654      +21     
=====================================================
  Files                    722      725       +3     
  Lines                  21974    22030      +56     
  Branches                1502     1503       +1     
=====================================================
+ Hits                    9720     9762      +42     
- Misses                 11731    11745      +14     
  Partials                 523      523              

☔ View full report in Codecov by Sentry.
📢 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.

[antoinemzs]

This looks like it might need a database migration to account for existing contracts not having the new field names (and having old ones that arent' recognised anymore)

[RomuDeuxfois]

This looks like it might need a database migration to account for existing contracts not having the new field names (and having old ones that arent' recognised anymore)

No migration is needed because contracts are automatically updated at application startup. This process ensures that existing contracts are aligned with the new field structures, handling both legacy fields and newly introduced ones seamlessly.