Fix deprecation replacements

[gutiory]

Some of the deprecation suggestions are not working when running Replace with action in Intellij. This is a bit annoying when we want to replace the deprecated method automatically.

The list of failed replacements is:

Either

Method	Working	Priority
all zip	NO
all	YES
bifoldLeft	YES
bifoldMap	NO
bimap	YES
bitraverseNullable	NO
bitraverseOption	NO
bitraverseValidated	NO
bitraverse	NO
catchAndFlatten	YES
catch	YES
combineK	YES
combine	YES
conditionally	YES
contains	YES
ensure	YES
exists	YES
filterOrElse	YES
filterOrOther	YES
findOrNull	YES
foldLeft	YES
foldMap	NO
fromNullable	YES
getOrHandle	YES
handleErrorWith	YES
handleError	YES
isEmpty	YES
leftIfNull	YES
orNone	YES
orNull	YES
orNull	YES
redeemWith	YES
redeem	YES
replicate	YES
replicate	YES
rightIfNotNull	YES
rightIfNull	NO
sequenceNullable	YES
sequenceOption	YES
sequenceValidated	YES
sequence (list)	YES
sequence (option)	YES
sequence	YES
tapLeft	YES
tap	YES
toEither	NO
traverseNullable	NO
traverse	NO
traverse	NO
void	YES
all zips	YES

Ior

Method	Working	Priority
foldLeft	YES
foldMap	YES
bifoldLeft	YES
bimap	YES
padNull	YES
orNull	YES
all	YES
exists	YES
findOrNull	YES
isEmpty	YES
isNotEmpty	YES
traverseEither	YES
traverseOption	YES
traverseValidated	YES
void	YES
getOrElse	YES
bisequence	NO
bisequenceEither	NO
bisequenceOption	NO
bisequenceNullable	NO
bitraverseValidated	NO
replicate	YES
replicate - Monoid	NO
sequence()	NO
sequenceEither	YES
sequence( Either )	NO
sequenceOption()	YES
sequence( Option )	NO
sequenceNullable()	YES
sequence( Nullable )	NO
sequenceValidated()	YES
sequence( Validated )	NO
leftWiden()	NO
zip (all)	NO
bifoldMap	NO
toValidated	NO
bicrosswalk	NO
bicrosswalkMap	NO
bicrosswalkNull	NO
bitraverse	NO
bitraverseEither	NO
bitraverseOption	NO
bitraverseOption	NO
bitraverseNullable	NO
bitraverseValidated	NO
crosswalk ( List )	NO
crosswalkMap	NO
traverse ( List )	NO
traverse ( Either )	NO
traverse ( Option )	NO
traverseNullable	NO
traverse ( Validated )	NO

[serras]

We already released 1.2.x, and the next is 2.0, so this issue is now outdated. Closing as a result.