API: deprecate legacy API in favour of Graph-based functional implementation

[martinfleis]

Closes #612

Adds decorators and custom warnings when decorator does not fit to remaining classes.

The only missing is NeighboringStreetOrientationDeviation. @u3ks what are we doing about that one?

@u3ks also, can you review this if I'm pointing to correct things?

[martinfleis]

Given we test the decorators and can silence these warnings, I am removing explicit checks from individual classes.

[codecov]

Codecov Report

Attention: Patch coverage is 96.62921% with 3 lines in your changes missing coverage. Please review.

Project coverage is 98.0%. Comparing base (4037c70) to head (b0bc871).
Report is 55 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #619     +/-   ##
=======================================
+ Coverage   97.4%   98.0%   +0.6%     
=======================================
  Files         26      38     +12     
  Lines       4328    6158   +1830     
=======================================
+ Hits        4214    6033   +1819     
- Misses       114     125     +11     

Files	Coverage Δ
momepy/dimension.py	98.8% <100.0%> (+0.1%)	⬆️
momepy/diversity.py	98.4% <100.0%> (+0.1%)	⬆️
momepy/intensity.py	99.5% <100.0%> (+<0.1%)	⬆️
momepy/shape.py	91.8% <100.0%> (+0.3%)	⬆️
momepy/tests/test_dimension.py	100.0% <100.0%> (ø)
momepy/tests/test_intensity.py	100.0% <100.0%> (ø)
momepy/tests/test_utils.py	99.4% <100.0%> (+0.1%)	⬆️
momepy/distribution.py	97.2% <92.3%> (-0.2%)	⬇️
momepy/elements.py	96.7% <85.7%> (-0.2%)	⬇️
momepy/weights.py	98.4% <83.3%> (-1.6%)	⬇️

[u3ks]

NeighboringStreetOrientationDeviation is missing.
I think the same functionality can be reimplemented using graph and then a call to Graph.apply.
But I dont think we can leave it to the user, since we got to define a custom apply function to take absolute difference, then mean.

[martinfleis]

NeighboringStreetOrientationDeviation is missing.

Can you look into that one?