feat: WebUI NEO start page basic layout

[ironAiken2]

This PR is about UI changing for Backend.AI WebUI NEO #2835

Changes:

• Added a start page utilizing the BAIBoard component.
• Added ActionItemContent component (can be used as primary action card for start page and subsequent pages)
• For responsive components, delete the descriptions of all cards if even one card causes scrolling.

! note

• The Cloudscape board component uses the Grid component internally. The braek point of a grid component is calculated based on the size of the container, not the window size, as follows ref
• The Cloudscape board component used for BAIBaord does not yet provide the ability to adjust columns per screen break point. ref

How to test:

• Navigate to start page (/start)
• Verify that the Button for each item is working properly.
• Verify that each item is repositioned correctly. (The Resize option is currently not allowed.
• In this PR, the default page has been changed from summary to start. We need to check if the redirect from error page to start is working properly, or if the refresh is working properly, etc.

Checklist: (if applicable)

• Mention to the original issue
• Documentation
• Minium required manager version
• Specific setting for review (eg., KB link, endpoint or how to setup)
• Minimum requirements to check during review
• Test case(s) to demonstrate the difference of before/after

[graphite-app]

Your org requires the Graphite merge queue for merging into main

Add the label “flow:merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “flow:hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[ironAiken2]

• refactor: Start page components #2885
• feat: WebUI NEO start page basic layout #2786 👈 (View in Graphite)
• chore: use pnpm patch in /react instead of patch-package #2661
• e2e: fix broken tests due to NEO mainlayout, Agent select and Image parsing #2851
• feat: NEO sider's toggle button and refactoring #2853
• feat: Main Layout NEO sider #2850
• feat: Global breadcrumb #2847
• feat: WebUILink and WebUINavigate component #2846 : 1 other dependent PR (#2858 )
• feat: Main layout NEO header #2844
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• flow:merge-queue - adds this PR to the back of the merge queue
• flow:hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Coverage report for ./react

St.❔	Category	Percentage	Covered / Total
🔴	Statements	5.24% (+0.03% 🔼)	395/7536
🔴	Branches	4.53% (-0.01% 🔻)	237/5236
🔴	Functions	3.14% (+0.02% 🔼)	78/2481
🔴	Lines	5.16% (+0.03% 🔼)	380/7369

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / ActionItemContent.tsx	0%	0%	0%	0%
🔴	pages/StartPage.tsx	0%	0%	0%	0%

Test suite run success

124 tests passing in 14 suites.

Report generated by 🧪jest coverage report action from 8ba4b61

[agatha197]

The interactive type is selected when I click the Start Batch Session button.

[ironAiken2]

The interactive type is selected when I click the Start Batch Session button.

resolved!

[YEONFEEL96]

Improved en-US and ko-KR description of each feature / button which shown in UI.
Some typos in ko-KR is also fixed.

For en-US, we will limit the use of 'a / the' on title to make is concise.
For ko-KR, we will limit the use of '~하기' in overall cases.

[YEONFEEL96]

Confirmed that my changes have been reflected. LGTM.

[agatha197]

LGTM

[yomybaby]

I tried to remove the default padding for board-item, but there are some issues.

�patch-package offical docs recommend using npm or yarn, and pnpm patch for pnpm. Since patch-package is patching based on package-lock.json, I don't think it's possible to use it with the current structure using pnpm. @yomybaby

There is draft PR which I created, please check it.
https://app.graphite.dev/github/pr/lablup/backend.ai-webui/2661/chore-use-pnpm-patch-in-react-instead-of-patch-package
Teams thread

[ironAiken2]

I tested it on pnpm patch PR and found it works fine, so I modified it to work based on pnpm patch. I've also fixed the scroll position issue. @yomybaby