Allow different default status per-plugin

Problem/Motivation

Some projects might need to set the status as published, others as unpublished, when a source string is discovered. It would be nice to be defined per-plugin. Then, by altering the plugin definitions, 3rd-party is able to modify this.

Proposed resolution

• Add a new status boolean optional property to TranslationType attribute defaulting to TRUE.
• In BabeStorage, when a new source string is inserted check if the hash already exists:
  • If the inserted source string is new (its hash doesn't exist yet in DB), create the hash with the (plugin) default status of the new string.
  • If existing source string status is TRUE, don't change it. Regardless of the (plugin) default status of the inserted string, the existing TRUE wins.
  • If existing source string status is FALSE, change the status to the (plugin) default status of the newly inserted string

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

New TranslationType definition property