Fix a problem with datetime format in rule contents

[joselsegura]

Description

Added a new way to parse the datetime format in order to allow the 2 different ones observed (with and without timezone)

Fixes #60

Type of change

• Bug fix (non-breaking change which fixes an issue)

Testing steps

Regular CI

[joselsegura]

CI is reporting in govet:

content/export_test.go:19:20: variable declaration copies lock value to Storage: github.com/RedHatInsights/insights-results-smart-proxy/content.RulesWithContentStorage

Anyone knows how to solve it? I don't find any other way to check if the rule content is properly parsed than this one in the test case...

[tisnik]

🐛 🔫

[Serhii1011010]

great

[natiiix]

LGTM

[codecov-commenter]

Codecov Report

Merging #63 into master will increase coverage by 3.42%.
The diff coverage is 58.33%.

@@            Coverage Diff             @@
##           master      #63      +/-   ##
==========================================
+ Coverage   33.49%   36.92%   +3.42%     
==========================================
  Files          10       12       +2     
  Lines         627      734     +107     
==========================================
+ Hits          210      271      +61     
- Misses        393      436      +43     
- Partials       24       27       +3     

Impacted Files	Coverage Δ
content/parsing.go	65.51% <58.33%> (ø)
content/content.go	46.93% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca4176f...558cff5. Read the comment docs.