Pack dashboard resources in release package about risingwave

[BugenZhao]

It appears that Dockerfile.hdfs is quite outdated. 😄 We've already switched to build the dashboard artifact in place since #12421.

risingwave/docker/Dockerfile

Lines 15 to 25 in 5a85fe9

	FROM base AS dashboard-builder
	RUN apt-get update && apt-get install -y curl gnupg protobuf-compiler && mkdir -p /etc/apt/keyrings \
	&& curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg \
	&& echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list \
	&& apt-get update && apt-get install -y nodejs
	COPY ./dashboard/ /risingwave/dashboard
	COPY ./proto /risingwave/proto
	RUN cd /risingwave/dashboard && npm i && npm run build-static && rm -rf node_modules

Specifically for this case, I would strongly suggest maintaining Dockerfile.hdfs as an extra step in Dockerfile to avoid such inconsistencies.

---

However, the issue still exist if there's no --dashboard-ui-path specified. We'll proxy to githubusercontent.com then at runtime and it's not versioned. This affect the users who directly download the binary directly or through Homebrew.

risingwave/src/meta/src/dashboard/proxy.rs

Lines 76 to 79 in 5a85fe9

	let url_str = format!(
	"https://raw.githubusercontent.com/risingwavelabs/risingwave/dashboard-artifact{}",
	path
	);

[BugenZhao]

Plan:

• Introduce a new crate dashboard to build the dashboard assets in the build script (build.rs) conditionally based on the configuration, providing a unified entry for serving dashboard assets.

  • Always build and embed in the binary for releases, requiring nodejs toolchain.
  • Do not build but proxy to GitHub for debug/CI builds, unless asked to build.

• The meta crate will depends on dashboard and be no more aware of the source of the dashboard assets. ui-path is deprecated as there's no need of external assets.