Fortran component build

[jdhughes-usgs]

Currently, from numpy.distutils.misc_util.Configuration is used to build Fortran components. This approach is currently deprecated. When running

python -m build

The following is reported:

`numpy.distutils` is deprecated since NumPy 1.23.0, as a result
  of the deprecation of `distutils` itself. It will be removed for
  Python >= 3.12. For older Python versions it will remain present.
  It is recommended to use `setuptools < 60.0` for those Python versions.
  For more details, see:
https://numpy.org/devdocs/reference/distutils_status_migration.html 

TODO:

• Find a solution that relies on setuptools.

Also, since it seems we are getting ~equivalent performance using numba maybe we should

1. only worry about fortran for development installation from the repo or
2. consider dropping fortran options to simplify pywatershed

[jmccreight]

I think we should adopt Fortran as develop only until we find some reason to motivate us or signal we should drop fortran.

The pathway from numba to fortran to compiled code is something I've enjoyed and maybe a reason Fortran sticks around, but maybe it's not necessary.

[jmccreight]

with #188 fortran compiles are only for editable installs.

[jmccreight]

pip 25 is going to deprecated legacy-editable installs and will force the issue at that time.
The fortran is no longer being tested in CI but is still available. Deprecation seems likely, pending some more performance comparisons against numba.