automatic-api

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

Could be useful to add (beside dbAuth.usernameColumn and dbAuth.passwordColumn) the possibility to configure the request fields (like dbAuth.usernameRequestField) to bind a specific request filed to the relative column of the auth table.

If I'm not mistaken the current state imposes username and password as mandatory fields for the request.

What would you like to be added:

It would be amazing to have a "Deploy with Heroku" button. Someone please help and build this.

https://devcenter.heroku.com/articles/heroku-button

Why is this needed:

Problem

• Some E2E tests are failing intermittently. For example, here is a CI job that failed but passed when re-ran.
• I'm theorizing that we're hitting Playwright's default 5-second timeout on some operations that take longer.

Solution

• I think we should raise the timeout value globally.
• Playwri