[DOC] Add Version Changed mark for new methods and arguments

[Zeroto521]

Add marks like note or summary to note users that these methods and arguments are newly added.
To avoid #1145.

sphinx has some marks

• versionchanged
  
• versionadded
  

mkdocs doesn't offer official marks.

• So we can use 3rd plugins for mkdocs like https://github.com/glennmatthews/mkdocs-version-annotations
• Or simply use summary (via !!! summary "Version Changed" or !!! summary "Version Added")
  
  

  pyjanitor/janitor/functions/min_max_scale.py

  Lines 99 to 103 in 9c02ab8

  	!!! summary "Version Changed"
  	- 0.24.0
  	- Deleted `old_min`, `old_max`, `new_min`, and `new_max` options.
  	- Added `feature_range`, and `jointly` options.

[samukweku]

@Zeroto521 how do we agree on the version number? Do we have a script that verifies this? breaking change and patches have different version numbers

[Zeroto521]

breaking change and patches have different version numbers

My experience is that both conditions use the major.mirror+1.0 as the version number.
Version construction: major.mirror.patch.

Such as the current pyjanitor version: 0.23.1. So use 0.24.0 to notify users that new features will come at that version.
Because we can't pre-know how many patch versions there will have.

pyjanitor/janitor/__init__.py

Line 32 in 9c02ab8

__version__ = "0.23.1"