Allow configuration for handling null and empty strings in translations (Fixes #456)

[alipadron]

This pull request introduces configuration options to control how null and empty string values are handled in translations. It also handles a case where the column value is null it returns null instead of empty string.

Background

• Pull request Keep the number of translations even with null values #427 introduced a change that allowed expecting null values where previously it would return an unexpected value. This was a positive change for future development.
• However, this caused issues for existing production deployments where code relied on the previous behavior.
• Pull request Revert "Keep null value" #428 reverted the changes introduced in Keep the number of translations even with null values #427.

Solution:

This pull request provides a solution that addresses both scenarios:

• Maintains the default behavior of the library.
• Introduces a configuration option to allow developers to explicitly return null and empty strings where expected.

Benefits:

• Existing codebases don't require immediate changes.
• Developers can now configure the library for specific needs.
• Improved flexibility and future-proofing.

[freekmurze]

Could you rebase against main?

[alipadron]

Could you rebase against main?

Done!

[freekmurze]

Thanks!