feat: dynamic object declaration

[josh-hemphill]

closes #102
All previous tests are passing, and relevant ones were made.
It seems to work reasonably well from what I can tell so far, I just emulated the behavior of how Arrays are handled to create an object key wildcard.
This would definitely have to be a major version change since there's a good chance this will break some people's implementation.

I also want to apologize for the ESLint changes, I have global ESLint and I was trying to prevent my global config from making sweeping stylistic changes.

[codecov]

Codecov Report

Merging #120 into master will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #120      +/-   ##
==========================================
+ Coverage   98.79%   98.89%   +0.10%     
==========================================
  Files           6        6              
  Lines         248      271      +23     
==========================================
+ Hits          245      268      +23     
  Misses          3        3              

Impacted Files	Coverage Δ
src/property.js	100.00% <100.00%> (ø)
src/schema.js	100.00% <100.00%> (ø)
src/utils.js	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 ed3f1ba...0c3be13. Read the comment docs.

[josh-hemphill]

I also had to create an object typecast function, which might not have ideal behavior, and probably should be in the same module the other typecasts come from; let me know if you want me to create a pull request for typecast or how I might improve the function.

[josh-hemphill]

I added tests for the two functions I missed.
I realized I shouldn't have modified the eslintrc, so I reverted that but had to add .vscode to the .gitignore.

@eivindfjeldstad Everything passes now and maintains code coverage.
Are there any tests you'd like me to add or major changes you'd like me to make?
Is this such a breaking change I should put it behind some kind of config in the instantiation of schemas? Or do you think it's consistent enough with the rest of the library's behavior it should just go with as is with a new semver major version increment?

[oychao]

Will this get merged and published soon? desperately needed.

[josh-hemphill]

Will this get merged and published soon? desperately needed.

There were compounding changes I needed, so I ended up creating josh-hemphill/valivar which is written in typescript and has dictionary/dynamic objects. It borrows heavily from this repo because I love the API.
So it should be compatible with code written for validate. Though I'm still working on the documentation.

Oh, and valivar also supports Deno