Resolve tsc via packageManager in custom resources

when using yarn workspaces, the node_modules typescript dependency is hoisted out of the backend/custom/** directories. in that case, path.join(targetDir, 'node_modules', '.bin', 'tsc') doesn’t exist.

using {packageManager.executable} run tsc allows the current package manager to resolve the dependency no matter what kind of configuration is currently set up

packages/amplify-category-custom/src/utils/build-custom-resources.ts

@@ -81,25 +81,14 @@ const buildResource = async (resource: ResourceMeta): Promise<void> => {
     }
   }
 
-  // get locally installed tsc executable
-
-  const localTscExecutablePath = path.join(targetDir, 'node_modules', '.bin', 'tsc');
-
-  if (!fs.existsSync(localTscExecutablePath)) {
-    throw new AmplifyError('MissingOverridesInstallationRequirementsError', {
-      message: 'TypeScript executable not found.',
-      resolution: 'Please add it as a dev-dependency in the package.json file for this resource.',
-    });
-  }
-
   try {
-    execa.sync(localTscExecutablePath, {
+    execa.sync(packageManager.executable, ['run', 'tsc'], {
       cwd: targetDir,
       stdio: 'pipe',
       encoding: 'utf-8',
     });
   } catch (error: $TSAny) {
-    printer.error(`Failed building resource ${resource.resourceName}`);
+    printer.error(`Failed building resource ${resource.resourceName} with TypeScript`);
     throw error;
   }