This partially reverts dbae950. With the ArticleFieldIDCreatedDate case restored, the explicit value of 415 for ArticleFieldIDEnclosure is no longer needed.

Co-authored-by: Eitot <[email protected]>

Only when there is a provided publication date on creation, use that one
without questioning it
Fix publication date not being transmitted by RefreshManager.m

Most dates interpretations/manipulations are now in Database.m
During fetching from feeds, we just retrieve the infos and store them in
relevant Article fields.
This makes the logic more apprehensible and easier to maintain.

Solves issue ViennaRSS#1749

Co-authored-by: Barijaona Ramaholimihaso <[email protected]>

Therefore, regarding dates, adopt in RSSFeed the same logic than in
AtomFeed.
Adapt RefreshManager to this unified logic.

As the meaning of `createddate` has changed, we have to adopt another
approach which provides similar (but not identical) results.

this allows the predicate editor to correctly re-load "date published" predicates.
Also, make the SmartFolder code better by extracting the repeated array of Date expressions and remove superfluous space in predicate translation strings