Support xml date/time nanoseconds

[tefra]

📒 Description

The built-in datatypes for xml date/time only go up to milliseconds.
The w3c defintions says that fractional seconds could be an arbitary number.

Resolves #678

🔗 What I've Done

• Updated the XmlDateTime, XmlTime to support up to nanoseconds (breaking compatibility change)

This shouldn't affect most people, that parse dates and then convert to the builtin python datetime/time objects, but if you construct the XmlDateTime/XmlTime manually and you used to pass milliseconds as a keyword argument, you will get an error. The argument now is called fractional_second and goes up to 999999999

💬 Comments

🛫 Checklist

• Updated docs
• Added unit-tests
• Sample tests pass
• W3C tests pass

[codecov]

Codecov Report

Merging #679 (5ee172c) into master (f837948) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #679   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           95        95           
  Lines         8259      8268    +9     
  Branches      1589      1590    +1     
=========================================
+ Hits          8259      8268    +9     

Impacted Files	Coverage Δ
xsdata/models/datatype.py	100.00% <100.00%> (ø)
xsdata/utils/dates.py	100.00% <100.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 f837948...5ee172c. Read the comment docs.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication