Allow TitleCase and camelCase

[tuethan1999]

Pull Request Description

Fixes #1761
implementation that allowed all variations of case and underscore: #1841

Feature Request

Provide convenience to a user by allowing them to pass a primitive name in either snake_case, TitleCase or camelCase

Implementation

Reduce TitleCase and camelCase into snake_case before matching them internally. This means we can't accept primitive names like "cOuNt" because it will be converted to "c_ou_nt". I think this is the desired behavior though

Assumptions:

• primitive name is camel case

[codecov]

Codecov Report

Merging #1854 (07d9102) into main (ec8a72b) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1854      +/-   ##
==========================================
+ Coverage   98.82%   98.83%   +0.01%     
==========================================
  Files         147      147              
  Lines       16290    16291       +1     
==========================================
+ Hits        16099    16102       +3     
+ Misses        191      189       -2     

Impacted Files	Coverage Δ
featuretools/synthesis/deep_feature_synthesis.py	98.62% <100.00%> (+0.38%)	⬆️
featuretools/synthesis/utils.py	100.00% <100.00%> (ø)
...ols/tests/synthesis/test_deep_feature_synthesis.py	99.32% <100.00%> (-0.01%)	⬇️
featuretools/tests/synthesis/test_dfs_method.py	99.54% <100.00%> (+<0.01%)	⬆️
featuretools/tests/utils_tests/test_gen_utils.py	100.00% <100.00%> (ø)
featuretools/utils/gen_utils.py	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 ec8a72b...07d9102. Read the comment docs.

[rwedge]

I would expect "Top3Words" to be converted to "top_3_words" but currently this will return "top3_words"

[rwedge]

A test just for the camel_and_title_to_snake method with a few inputs could be good

[tamargrey]

Is there somewhere in the documentation that we can put the new constraints on what primitive strings will be recognized? I guess we never specifically mentioned that they had to me the same as primitve.name in the past, but now that there's more than one valid option, it might be nice to have the information written down somewhere.

[tamargrey]

@dvreed77 Not sure if we need to handle this case, but wanted to note a potentially problematic string for camel_and_title_to_snake: "NaN". Something like ft.utils.gen_utils.camel_and_title_to_snake('hasNaNs') results in has_na_ns.

I think we can avoid dealing with this specific example if we just use the word "Null" an time we might use "nan" in a primitive name, but it's something to keep in mind bc we can't stop users from trying to pass in that string

[rwedge]

can we include a snake case test case to confirm snake case passed in is unaltered?

[dvreed77]

done

[rwedge]

LGTM