EPIC Supporting All WW Types

We have good coverage for what I would call the "default" woodwork types like Double, Boolean, Datetime, NaturalLanguage but how should we handle non-default types that represent more specific data types, e.g.

- Other logical types with string physical type -- Address, EmailAddress, Filepath, PersonFullName, PhoneNumber, URL
- Other categorical types with category semantic tag -- PostalCode, SubRegionCode, CountryCode
- LatLong
- Ordinal
- Timedelta

This epic tracks work related to supporting these types in evalml.

This touches on the broader concept of where the division between feature tools and evalml should be. A big question we'll have to answer is whether evalml should create features for these datatypes or it should be assumed that features were created beforehand.