some improvements regarding pandas 2.2.x futurewarnings and error raises

[SteffenMeinecke]

@vogt31337 @KS-HTK @mfranz13 I guess we have not yet started to fix the 2.2.x FutureWarnings for pandas 3 behavior. Here, I started for that short time I had. You can have a look and comment on whether you like my proposal to concat DataFrames with empty_defaults_per_dtype() or not. Regarding the FutureWarning of fillna() and replace(), I like to reference this post which helped me a lot.

[mfranz13]

@SteffenMeinecke I think this is a good approach. Would you mind adding a test?

[SteffenMeinecke]

@SteffenMeinecke I think this is a good approach. Would you mind adding a test?

I fear, I won't have time in the near future.

[SteffenMeinecke]

@KS-HTK, thanks for approving the previous state. Can you please merge when the tests have passed?

[codecov]

Codecov Report

Attention: Patch coverage is 76.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 75.87%. Comparing base (f6763c7) to head (9c889e3).
Report is 13 commits behind head on develop.

Files with missing lines	Patch %	Lines
pandapower/auxiliary.py	60.00%	4 Missing ⚠️
pandapower/sql_io.py	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2477      +/-   ##
===========================================
- Coverage    75.88%   75.87%   -0.02%     
===========================================
  Files          284      284              
  Lines        33662    33682      +20     
===========================================
+ Hits         25546    25556      +10     
- Misses        8116     8126      +10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.