Architectural reasons for not permitting queries or mutations as HTTP action handlers
🎁Feature Request
I wonder if there are deep architectural reasons for the fact that Convex query and mutation functions are not permitted as HTTP action handlers: https://discord.com/channels/1019350475847499849/1495054476933992449/1495054476933992449 , or this is a more or less random limitation? My app has an HTTP API endpoint with very high call volume. The API is essentially a query. Because HTTP action handler should be an action that calls to the query, the billed "function calls" in Convex is doubled (the HTTP handler itself + the query), which would be avoidable if the action handler was a query.
