Fix Escaped Characters in Timestamp Format Resulting in Forced Update Even when It Should Not

[pjkaufman]

Fixes #1411

There seems to be a bug in moment where parsing values with escaped characters in strict mode means the result will not be valid even if it was generated using the format used to parse it. So we need to handle things a little differently to allow that logic to work.

Changes Made:

• Added a test for the scenario in question
• Updated the logic for moment parsing and comparisons to not use strict and instead double check the output value of comparing the moment parsed value converted back to the original format and the original value to make sure they are the same