better description for limit in api

[Bowrna]

I have made changes in config.yml file with better description for maximum page limit and fallback page limit
closes: #27425

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

I agree it was confusing and the way it is described now is vey accurate. Thanks @Bowrna for that.

Additionally - maybe that would be an option to consider as a follow-up we could print (if not already done) warning in webserver's logs in case someone uses page limit higher than maximum? This way there would be at least an indication in the logs that someone is doing something not really expected and the admins of Airflow could potentially warn the user of the API about it.

[Bowrna]

I agree it was confusing and the way it is described now is vey accurate. Thanks @Bowrna for that.

Additionally - maybe that would be an option to consider as a follow-up we could print (if not already done) warning in webserver's logs in case someone uses page limit higher than maximum? This way there would be at least an indication in the logs that someone is doing something not really expected and the admins of Airflow could potentially warn the user of the API about it.

yes completely agree with you on this point @potiuk There is high chance for user to miss out reading the description. Throwing this information in the logs is the best way to prevent such confusion. I will do that part.