fix: ignore translations from frappe and erpnext

Don't write translatable strings into HRMS's .pot-file for messages that are already specified in the Frappe Framework or ERPNext. If a translatable string exists there, we don't want to override it with our own.