Error while Deploying Developer Portal as a Static WebApp.

> [!IMPORTANT]
> **PLEASE DO NOT CREATE ISSUES RELATED TO MANAGED DEVELOPER PORTAL IN THIS REPOSITORY**. Issues related to "Managed developer portal" will be closed automatically. Managed developer portal issues should be created directly in Azure Support + Troubleshooting in Azure portal. Contact Azure support (or) submit a post [on Stack Overflow](http://aka.ms/apimso). Feature requests can be raised [on the Azure Feedback Forum](https://aka.ms/apimwish).

Every self-hosted developer bug report should have precise description and reproduction steps; console traces (or) source code references are appreciated.

## Bug description

Issue while deploying the Developer portal as Self hosted developer portal as a Static Web App. We copied the GitHub repository to Azure DevOps and referenced it to the Static Web app. But while deployment pipeline threw the below error:

<--- Last few GCs --->

[216:0x303ad250] 189495 ms: Scavenge (reduce) 2041.7 (2082.9) -> 2041.5 (2083.2) MB, 9.07 / 0.00 ms (average mu = 0.155, current mu = 0.006) allocation failure;
[216:0x303ad250] 189535 ms: Scavenge (reduce) 2042.1 (2083.2) -> 2041.9 (2083.2) MB, 12.62 / 0.00 ms (average mu = 0.155, current mu = 0.006) allocation failure;
[216:0x303ad250] 189578 ms: Scavenge (reduce) 2042.4 (2083.2) -> 2042.2 (2083.7) MB, 9.89 / 0.00 ms (average mu = 0.155, current mu = 0.006) allocation failure;

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0xb8cf03 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [webpack]
2: 0xf04140 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
3: 0xf04427 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
4: 0x1116075 [webpack]
5: 0x1116604 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [webpack]
6: 0x112d4f4 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [webpack]
7: 0x112dd0c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
8: 0x1104011 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
9: 0x11051a5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
10: 0x10e27f6 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack]
11: 0x153e336 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [webpack]
12: 0x7f6104e99ef6
Aborted (core dumped)

## Reproduction steps

1. Go to 'Azure Portal'
2. Search for 'Static Web App'
3. Click On 'Create'
4. Enter Details and create the webapp.

## Expected behavior

It will create an yml pipeline and execute and deploy the developer portal as a static webapp.

## Is self-hosted portal?

Yes
> [!WARNING]
> "Managed developer portal issues" will be closed automatically. See above for more details.

## Release tag or commit SHA (if using self-hosted version)

[e.g., release `2.0.0`, commit `c45da9778b70d369aba60fa2e63c191efe2b548f`]

## API Management service name

[e.g., contoso-api]

## Environment

- Operating system: [e.g., iOS]
- Browser: [e.g., Google Chrome, Safari]
- Version: [e.g., 22]

## Additional context

Add any other context about the problem here, including screenshots.

Start with the Azure Portal Static Web App creation steps and reproduce the Azure DevOps deployment pipeline that ends with the webpack JavaScript heap out-of-memory trace. The payload names no repository files, tests, release tag, commit, or environment details; done would mean identifying a reproducible deployment path that completes successfully.

Written by the indexing model from the issue text.