Create 0.2.0 release

[veenstrajelmer]

The goal of this tag/release is to reduce the complexity for the user by making the public functions straightforward to use. There will be no changes that significantly affect the results, so we can still (approximately) reproduce the kenmerkendewaarden 2011/2021 derived in 2020-2022. The resulting methods are still not production-ready, since there are still improvements needed that will be inplemented in kenmerkendewaarden 0.3.0.

Todo:

• update kwk data retrieval #5
• improve kwk data retrieval #12
• convert all onenote notes to issues
• add to readme description: https://www.rijkswaterstaat.nl/water/waterbeheer/metingen/meten-bij-rijkswaterstaat/waternormalen#:~:text=Kenmerkende%20waarden%20zijn%20voor%20veel,laatste%20jaar%20is%20onvoldoende%20representatief. (And more online references)
• add warning: still under development, release will contain official version
• update dependencies after hatyan 2.8.0 release #27
• refactor code #30
• Add devtools to repos #35
• refactor KWK_process.py #32
• increase test coverage
• central check for timeseries completeness #58
• use improved timedelta formater in havengetallen plotting functions #77
• gemgetij: validation data is not in timedelta so cannot be compared with new timedelta axis
• link issues that are not yet linked to release issue (or link to 0.3.0 issue)
• Refactor and reproduce overschrijdingsfrequenties method #26
• create issues from all TODO in KWK_process.py and underlying functions
• Inconsistent lengths between compute_actual_counts and compute_expected_counts in case of all-nan year/month #83
• clearer error messages for slotgem #82
• add hydra-nl testcase for overschrijdingsfreqs #90
• wrapup refactoring of gemiddeldgetij method #92
• attach station attribute #94
• add additional logging info messages in modules
• improve docstrings for public functions #97
• simplify validation gemiddeldgetij lines in kwk_process.py #99
• add overschrijding hydra statistics #39
• compare station attribute in plot_overschrijding() #95
• improvements in output csvs for dashboards #17
• derive preliminary output 2011 and 2021 for station_list = ["VLISSGN","HOEKVHLD","IJMDBTHVN","HARLGN","DENHDR","DELFZL","SCHIERMNOG","VLIELHVN","STELLDBTN","SCHEVNGN","ROOMPBTN"]
• Automatic removal of duplicated timesteps #114
• Consider catching empty measurement dataframes #115
• reduce netcdf filesizes #118
• if re-retrieving data, also update timezone of tstart/tstop: retrieve data in MET instead of UTC #120
• re-retrieve data to get smaller filesizes after reduce netcdf filesizes #118
• catch zero stations in kw.retrieve_measurements() #122
• Catch zero-length extremes data_pd_HWLW_10y_12 df for STELLDBTN #125
• align dtypes of variables returned by different kw functions #111
• align argument names for functions #128
• add escape for almost-time-duplicates #130
• derive kenmerkendewaarden for 2011 and 2021 and compare results

Tasks not related to methods (maybe partly for next tag/release):

• report TimeSeries_TimedeltaFormatter_improved to pandas >> commented in Better display of negative Timedelta pandas-dev/pandas#17232 (comment)
• consider applying black #112
• fix PerformanceWarning about fragmented dataframe (pytest python 3.9 and 3.12) Deltares/hatyan#272 >> very present when using pandas>=2.2.0
• check warnings in pytest workflow: fix numpy and pandas deprecationwarning Deltares/hatyan#319
• fix "metodieken" typo in readme
• consider updating whatsnew for PR's between 87 and 116
• tag+release v0.2.0
• release on pypi and add supported-py-versions badge and pypi-package-version badge and number-of-downloads badge. Maybe move to 0.3.0 release? Will AB use tidalindicators etc?
• produce 2011/2021 results, zip+backup files and send to RWS

Follow-up: #75