refactor: replaced moment with dayjs

[GoPro16]

BREAKING CHANGE: moment has been replaced

All of the existing tests that cover the date validation work. The only downside is that we will have to release as a BREAKING CHANGE since some users can rely upon moment in other areas of their projects since its a required dep here.

closes #125

[netlify]

Deploy preview for availity-reactstrap-validation ready!

Built with commit fbc7b66

https://deploy-preview-126--availity-reactstrap-validation.netlify.com

[TheSharpieOne]

I don't think this is a breaking change. We don't expose the underlying date library. It doesn't change the API this library exposes or it's usage/results. If someone is depending on something without it being in their owns deps... then that is their fault.

[GoPro16]

For some reason dayjs customParseFormat is able to parse an invalid parse format to a valid date.

availity-reactstrap-validation/__test__/AvValidator.date.spec.js

Lines 69 to 71 in 897a4af

	it('should ensure the format matches the customized format', () => {
	expect(fn('10/12/2014', context, {format: 'YYYY-MM-DD'}, input)).to.equal('Format needs to be YYYY-MM-DD');
	});

availity-reactstrap-validation/__test__/AvValidator.date.spec.js

Lines 45 to 47 in 897a4af

	it('should ensure the format matches the customized format', () => {
	expect(fn('10/12/2014', context, {format: 'YYYY-MM-DD'}, input)).to.equal('Format needs to be YYYY-MM-DD');
	});

Passing in 10/12/2014 with parse format of YYYY-MM-DD results in the valid date of 08-14-2015

Not sure why this is happening but I am going to open an issue on dayjs for this.

[GoPro16]

Created issue here: iamkun/dayjs#555

[robmcguinness]

Fixed in https://github.com/iamkun/dayjs/releases/tag/v1.8.13