Translate and fix fallback errors when creating or updating OC

[kristinalim]

What? Why?

Closes #2641

This translates the fallback errors when creating or updating an OC fails. Fallback, because some errors that we explicitly support in the code (e.g. when close date is set before open date) give a more specific error.

Then, for the error when updating, this was actually saying "Failure to create order cycle" (should be "update"). This has also been addressed.

What should we test?

One way I let these errors appear is by removing authorization of a user for an enterprise while the user is filling in the OC form.

@RachL if you know a simpler way, kindly share. It's likely that when you encountered these errors after leaving some fields blank was only because staging had inconsistent data as @luisramos0 found. I couldn't get these errors to appear that way.

1. Browser Session 1: Add test user as manager to an enterprise.
2. Browser Session 2: As test user, open the new OC page and fill in the form, but do not submit.
3. Browser Session 1: Remove test user as manager for the enterprise.
4. Browser Session 2: Being unauthorized for the enterprise now, test user should get the translated error when submitting the form.

Repeat the same for editing an OC.

Release notes

• Fix and translate fallback errors when creating and updating an order cycle

Changelog Category: Fixed

[luisramos0]

Approving this PR as we have agreed the convention is to keep js translations under js to reduce assets size.
We need to:

• create issue to represent the clean up - moving js existing translations under js
• create issue to change the assets pipeline to incude only translations under js
• write this convention on wiki

[kristinalim]

I created issues openfoodfoundation/wishlist#342 and #2722, and also added the section "Javascript translations: Put translation key under the "js." namespace" to the i18n wiki page.

There are already 2 code review approvals here, so moving to "Test Ready".

[sstead]

Testing notes

The error messages appeared correctly in English. One note, the message read 'failed to create OC' regardless of whether the use is trying to create or edit an order. I don't think this really matters, but I suppose one could say 'failed to edit OC'

https://docs.google.com/document/d/1Ikt8tJ1gYX-a1Mmtpgp6B99XbapRz5y92wicmrQAnTA/edit#heading=h.xw2hpxaxawc9

[mkllnk]

There should be two error messages:

• "Failed to create order cycle"
• "Failed to update order cycle"

Actually, I just checked the code and if see only the create error, then this pull request doesn't work properly. Let me check.

[kristinalim]

@mkllnk I suspect this hasn't been staged yet.

[mkllnk]

I deployed it again and re-tested: it works.

[sstead]

Testing Notes

There are unique error messages now- "failed to update" and "failed to create"

https://docs.google.com/document/d/1Ikt8tJ1gYX-a1Mmtpgp6B99XbapRz5y92wicmrQAnTA/edit#

[luisramos0]

hey @kristinalim I just now saw the issues to move translation to js namespace and also the wiki update. great stuff, thanks!