Create a new step: `config-features`?
See https://github.com/huggingface/datasets-server/issues/2215: the `features` part can be heavy, and on the Hub, when we call /rows, /filter or /search, the features content does not change; there is no need to create / serialize / transfer / parse it.

We could:
- add a new /features endpoint
- or add a `features: bool` parameter to all the endpoints that return rows to include the features in the response.

The only exception is when a new commit happens, and the features have changed. But the Hub could check the `X-Revision` value and reload the page in case of a mismatch.
Create a new step: `config-features`?: See https://github.com/huggingface/datasets-server/issues/2215: the `features` part can be heavy, and on the Hub, when we call /rows, /filter or /search, the features content does not change; there is no need to create / serialize / transfer / parse it.

We could:
- add a new /features endpoint
- or add a `features: bool` parameter to all the endpoints that return rows to include the features in the response.

The only exception is when a new commit happens, and the features have changed. But the Hub could check the `X-Revision` value and reload the page in case of a mismatch.