fix: make env optional in ResourceFieldEntry TypeScript type

Aligns the TS interfaces with the JSON schema change from 39613f5 that
removed the `required: ["env"]` constraint. Fields like `branch` and
`database` in the lakebase manifest don't map to env vars.

Signed-off-by: Pawel Kosiec <pawel.kosiec@databricks.com>

Author: pkosiec

packages/appkit/src/registry/resource-registry.ts

@@ -315,6 +315,7 @@ export class ResourceRegistry {
       const values: Record<string, string> = {};
       let allSet = true;
       for (const [fieldName, fieldDef] of Object.entries(entry.fields)) {
+        if (!fieldDef.env) continue;
         const val = process.env[fieldDef.env];
         if (val !== undefined && val !== "") {
           values[fieldName] = val;

packages/appkit/src/registry/types.ts

@@ -58,7 +58,7 @@ export {
  */
 export interface ResourceFieldEntry {
   /** Environment variable name for this field */
-  env: string;
+  env?: string;
   /** Human-readable description for this field */
   description?: string;
   /** When true, this field is excluded from Databricks bundle configuration (e.g. app.yaml) generation. */

packages/shared/src/plugin.ts

@@ -101,7 +101,7 @@ export interface PluginManifest {
  */
 export interface ResourceFieldEntry {
   /** Environment variable name for this field */
-  env: string;
+  env?: string;
   /** Human-readable description for this field */
   description?: string;
   /** When true, this field is excluded from Databricks bundle configuration (e.g. app.yaml) generation. */