Convert Enzyme test to RTL in Azure Monitor InsightsConfig

Requirement for Grafana to move to React 18 (see grafana/grafana#48253)

Improve documentation

Link

Not just this Link, This should be done through out the whole docs.
https://supabase.com/docs/guides/auth

Describe the problem

Supabase dashboard in videos and images are outdated and need to be updated for better ease of use.

Describe the improvement

Update the videos and images from the old dashboard to the new dashboard.

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

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

Describe the Bug

The JSON response sent back over HTTP doesn't encode certain characters correctly.

For example, if a value in a string column contains the char \1 the byte value is copied verbatim in the response, breaking the client:

>>> json.loads('"\1"')
...
json.decoder.JSONDecodeError: Invalid control character at: line 1 column 2 (char 1)

Instead, we shou

The macros can emit code directly referencing serde_json::Value which may trigger compilation errors if the user doesn't have it in their own dependencies: https://discord.com/channels/665528275556106240/665528275556106243/969377568685981716

I'm surprised we haven't encountered this before now, probably because if someone wants to use serde_json::Value in their code deliberately then they p

{
  "Checksum": 0,
  "FlagBits": 0,
  "Sections": [
    {
      "Document": {
        "$k": [
          "listDatabases",
          "nameOnly",
          "$db"
        ],
        "listDatabases": 1,
        "nameOnly": null,
        "$db": "admin"
      },
      "Kind": 0
    }
  ]
}

nameOnly is documented to be a boolean, but at least [one real application](htt

These files when added magically but not part of git tracked files causes update failure.

reference: frappe/bench#1225

related: frappe/frappe#16616 (you'll find which function create this file in this PR)

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi