We originally had IntegerNullable and Integer because EvalML relies on estimator/classifiers that do not support the pandas Int64 dtype (which is used in IntegerNullable)
However, a better long term solution is for Woodwork to have 1 Integer type that supports nullable values
For this issue
Remove/Deprecate IntegerNullable
Change the Integer physical type from int64 to Int64
Update inference logic to account for this change
Verify that Featuretools and EvalML can properly handle this change
Int64
dtype (which is used in IntegerNullable)int64
toInt64