[docs] Improve schema.json

[lorenzolewis]

There are a few things in the schema that could be updated (based on tauri-apps/tauri-docs#604). File for reference: https://github.com/tauri-apps/tauri/blob/dev/tooling/cli/schema.json

We should also be aware of any down-stream impacts and keep in mind increasing quality there (such as the VS Code extension). I'm willing to do this myself once I have some spare time

• "HttpAllowlistScope" description
• Fix link in ShellAllowlistConfig.sidecar description
• This should be marked as optional, not an array of types

  tauri/tooling/cli/schema.json

  Lines 409 to 411 in 3e702cf

  	"type": [
  	"string",
  	"null"

• Escape brackets in description

  tauri/tooling/cli/schema.json

  Line 653 in 3e702cf

  "description": "Specifies the maximum number of values are for this argument. For example, if you had a -f <file> argument where you wanted up to 3 'files', you would set .max_values(3), and this argument would be satisfied if the user provided, 1, 2, or 3 values.",

• These newlines cause an issue when rendering in a table, should be a break instead

  tauri/tooling/cli/schema.json

  Line 408 in 3e702cf

  "description": "A shell command to run before `tauri build` kicks in.\n\nThe TAURI_PLATFORM, TAURI_ARCH, TAURI_FAMILY, TAURI_PLATFORM_VERSION, TAURI_PLATFORM_TYPE and TAURI_DEBUG environment variables are set if you perform conditional compilation.",

• This link is broken

  tauri/tooling/cli/schema.json

  Line 1361 in 3e702cf

  "description": "The Content Security Policy that will be injected on all HTML files on the built application. If [`dev_csp`](SecurityConfig.dev_csp) is not specified, this value is also injected on dev.\n\nThis is a really important part of the configuration since it helps you ensure your WebView is secured. See <https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP>.",

[lorenzolewis]

If someone could give me a bit of context in the meantime it would help (pointing me in the direction of how/where this is generated and any other downstream impacts such as the VS Code extension I should test out)

[lucasfernog]

The schema is generated using schemars, you can see the usage in the structs on the config source code. @lorenzolewis

[lucasfernog]

You can regenerate the schema by running cargo build in the tooling/cli folder. Just make any changes you wish, and you can verify how it looks on VS Code by opening examples/api/src-tauri/tauri.conf.json and hovering any of the fields.

[lucasfernog]

Since the schema is automated, we should probably do a post processing here for newlines and etc.