Fixed #23668 -- Changed make_aware() and make_naive() to use the current timezone by default

When calling `make_aware()`, either `get_current_timezone()` or `get_default_timezone()` seem to be a logical default. In my opinion, `get_current_timezone()` is seems more correct most of the time. That is, when handling a naive datetimes, converting it to the current time zone is the most typical operation. This change makes using `make_aware()` easier to use as it will now generally do the right thing by default. If the user wants to use a different timezone, the option is still available.
This looks good to me, assuming Aymeric gives his +1. I'm just going to change this sentence to "In older versions of Django, timezone was a required argument." in order to better describe how the new behavior described above differs from the past.