Add warning when negative bev availability profile values

[tgi-climact]

Changes proposed in this Pull Request

Changing the bev_avail_max and bev_avail_mean values could cause the profile to generate negative values. This leads to infeasibility. Raising a warning earlier in the process is useful to catch the configuration error sooner. This warning is raised in build_transport_demand.

Checklist

• I tested my contribution locally and it seems to work fine.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in all of config.default.yaml.
• Changes in configuration options are also documented in doc/configtables/*.csv.
• A release note doc/release_notes.rst is added.

[fneum]

It would be good to understand where the negative values could come from and fix the underlying issue.

[tgi-climact]

It would be good to understand where the negative values could come from and fix the underlying issue.

In my case, I was defining a too high value for bev_avail_max compared to bev_avail_mean. If so, avail becomes negative here :

avail = avail_max - (avail_max - avail_mean) * (traffic - traffic.min()) / (
        traffic.mean() - traffic.min()
    )

Because it's configuration based, I'm afraid there's not that much to do other than raise a warning.