Platform configuration options for enabling development support.

| Field | Type | Description | Default |
|---|---|---|---|
| `vsock_development` | `bool` |   |   |
| `tracing` | `https://fuchsia.dev/reference/TracingConfig` | Configure tracing. Note: \\\[\`DevelopmentSupportConfig::include_tracing\`\] must be \`true\` for tracing to be available. |   |
| `tools` | `https://fuchsia.dev/reference/ToolsConfig` | Tools to enable along with development support |   |
| `include_tracing` | `bool` | Override tracing inclusion on the target. |   |
| `include_sl4f` | `bool` | Whether to include sl4f. |   |
| `include_netsvc` | `bool` | Override netsvc inclusion on the target. Follows the same resolution as \`enabled\` if absent. |   |
| `include_devscreen` | `bool` | Whether to include \`devscreen\`, a readable boot dashboard for display-only builds that would otherwise show the virtual console's logo tab. Off by default; not allowed on user builds. |   |
| `include_bootstrap_testing_framework` | `bool` | Whether to include the bootstrap testing framework which will allow running tests in a bringup-like environment using the run-test-suite command line tool. |   |
| `include_bin_clock` | `bool` | Include the bin/clock program on the target to get the monotonic time from the device. TODO(b/309452964): Remove once e2e tests use: \`ffx target get-time\` |   |
| `heapdump` | `https://fuchsia.dev/reference/HeapdumpConfig` | Configure Heapdump memory profiling. |   |
| `enabled` | `\[bool]` | Override the build-type enablement of development support, to include development support in userdebug which doesn't have full development access. If nothing is provided, a reasonable default is used based on the build type. |   |
| `enable_userboot_next_component_manager` | `bool` | Enable userboot.next for running a boot-time test. Only valid on eng builds. |   |
| `enable_netsvc_netboot` | `bool` | Enable the netboot feature of the netsvc |   |
| `authorized_ssh_keys_path` | `Option` | Path to a file containing ssh keys that are authorized to connect to the device. |   |
| `authorized_ssh_ca_certs_path` | `Option` | Path to a file containing CA certs that are trusted roots for signed ssh keys that are authorized to connect to the device. |   |