fix: Avoid logging kind: {kind} is deprecated...` if the corresponding replacement is in place

[edgarrmondragon]

This would make the migration smoother since the Hub could do a batch update that's backwards compatible. Older versions of Meltano (I think, yet to confirm) wouldn't crash if an unknown setting attribute such as sensitive is present.

---

@danielptv I think keeping both is the most sensible. We could update Meltano to only log the warnings when the corresponding future replacement is not in place.

Originally posted by @edgarrmondragon in meltano/hub#1675 (comment)

[edgarrmondragon]

Confirmed that Meltano 2.x doesn't complain about sensitive: true being present in the plugin definition.

Installing and preserving Meltano 2.x

$ pipx install 'meltano==2.*' --python python3.11 --suffix=@2                                                                                                                                                                                                        
  installed package meltano 2.20.0 (meltano@2), installed using Python 3.11.7
  These apps are now globally available
    - meltano@2
done! ✨ 🌟 ✨

$ pipx upgrade-all --skip meltano@2                                                                                                                                                                                                                                  
Versions did not change after running 'pipx upgrade' for each package 😴

$ meltano@2 --version                                                                                                                                                                                                                                                
meltano, version 2.20.0

[edgarrmondragon]

The batch update in question: meltano/hub#1696. Thanks to @pnadolny13!