XSDuration in EWSUtilities fix

[ghost]

This pull request fixes the problem with wrong parsing of Bias in Period.(#357, #398 and #343)

Problem:

• TimeSpan for this one -PT3H30M will be parsed as:

negative true
year 0
month 30
day 0
hour 3
minute 30
seconds 0

• The big M for months and minutes seems to be correct according to ISO 8601 and the only difference is 'T' in the middle. For example this one P1Y2M10DT2H30M is a correct Time interval.

Fix:

• For parsing of TimeSpan, an Joda-Time Period is now used instead of row Java Regex.
• Period.parse() can automatically parse any value in form P1Y2M10DT2H30M, except of leading '-' symbol. For parsing '-' Java Regex is still used.
• Two method getXSDurationToTimeSpan() and getXSDurationToTimeSpanValue() are merged in one getXSDurationToTimeSpan(), because Joda-Time can parse duration with years and months too.
• Joda-Time can also parse values like PT2H100M59.0S, the minutes are bigger then 60. This duration will be parsed in to PT3H40M59.0S

Test:

• Corresponding tests are added to new class TimeSpanUtilsTest

[azurecla]

Hi @itbw, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.

TTYL, AZPRBOT;

[vboctor]

Remove extra blank lines.

[vboctor]

Thanks @itbw for your contribution. 👍

[pathikrit]

👍

[vbauer]

👍

[serious6]

@itbw thanks for your contribution.

[serious6]

referenced issues have been closed.