Implement "CLI engine crash reporting" for Formatter Engine and `getConfig` and `getDmmf` of Query Engine

This relies on https://github.com/prisma/prisma/issues/12493 and https://github.com/prisma/prisma/issues/12494 being implemented. (Done)

We want to implement error reporting similar to how we already have it for Migration and Introspection Engine crashes for the Formatter Engine and QueryEngine (getConfig and getDmmf parts). Via the above mentioned issues the necessary mechanisms in the engines have been implemented, and can now be used here as well.

1. • Allow triggering the new debug functionality (implemented via #12493 and #12494) similar to e.g. in Migrations with an environment variable.
   • (Note that we want to be able to trigger getConfig and getDmmf crashes separately, so they need a different “trigger” on the CLI side as they are often called together or close to each other.)
   • If one of the issues is not implemented yet, just fake the code so pretend it was already there - and we can add the actual implementation later.
2. • Make sure errors are correctly thrown so error handling UI can be triggered to start upload process etc (Internal documentation: https://www.notion.so/prismaio/CLI-Engine-Crash-Reporting-7bad95ea3c5a45f4a5a3250755a324a5#606a4379530c46e1bcd9cd12b107f221)
3. • Implement CLI Engine Error handling for all uses of Formatter Engine and QueryEngine (getConfig and getDmmf)
4. • Add tests similar to existing IE and ME error triggering to make sure this keeps working
5. • To be documented at https://www.notion.so/prismaio/CLI-Engine-Crash-Reporting-7bad95ea3c5a45f4a5a3250755a324a5#a44d5d144e144d00920fb2e4d90dfac3 and https://github.com/prisma/prisma/pull/13359

[jkomyno]

I have locally added the --enableTriggerPanic flag to the query-engine cli get-config and cli dmmf commands. Here is an example @janpio:

[jkomyno]

The fancy error reporting (i.e., handlePanic) is only triggered whenever an error with a rustStack property is bubbled up in the cli. Locally, I have propagated the errors for getConfig and dmmf whenever either the FORCE_PANIC_QUERY_ENGINE_GET_CONFIG=1 or the FORCE_PANIC_QUERY_ENGINE_GET_DMMF=1 env variables are set. However, I still have to capture the Rust’s stacktrace and embed them in an Error the way @prisma/cli wants it.