[TECHNICAL SUPPORT] LPS-44439 Localized VARCHAR2 fields can exceed their maximum length

Ray, I would like you to look at this pull request that I received. Localized fields usually have 4.000 characters at most and we validate that lenght in the backend, but the xml itself introduces more characters and therefore in some situations there is a database exception.

This pull makes the journal content field bigger and the asset publisher one, but I am wondering if this problem only affects Journal or if we should:
a) extend this to all localizable fields
b) validate the length of the field to include the xml overhead before sending it to the database in the Journal Article validation
c) accept this pull as it is, since it may be enough for now.

Thanks!

cc @giros @zsagia