Enforce strict missing translations

[CuddlyBunion341]

In ShapeHub, we encountered an issue where a model label wasn't translated, and our tests failed to address this. Relying on the model's human-readable attribute is prone to errors. I believe translations should be explicitly defined.

Rails 8 Introduced the following:

config.i18n.raise_on_missing_translations
Determines whether an error should be raised for missing translations. If true, views and controllers raise I18n::MissingTranslationData. If :strict, models also raise the error. This defaults to false

With config.i18n.raise_on_missing_translations = true:

shapehub(dev)> Croms::Patient.human_attribute_name(:consent)
=> "Consent"

With config.i18n.raise_on_missing_translations = :strict:

shapehub(dev)> Croms::Patient.human_attribute_name(:consent)
(shapehub):1:in '<main>': Translation missing. Options considered were: (I18n::MissingTranslationData)
- en.activerecord.attributes.croms/patient.consent
- en.attributes.consent

        raise exception.respond_to?(:to_exception) ? exception.to_exception : exception
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[CuddlyBunion341]

Ignore md-book. It has been failing for quite some time.

[sislr]

Ignore md-book. It has been failing for quite some time.

do we still need it? content is now outdated since CD fails, right? I'd get rid of it

[rnestler]

Ignore md-book. It has been failing for quite some time.

Fix it, not ignore it!

[rnestler]

Fixed it for you: #430

[rnestler]

For English applications it may be overkill and the fallbacks would work fine, but since most of our apps are German or multilingual I think it's a good default.