ci: dev-build with large page size

[MichaelScofield]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

sometimes our customer wants to test greptimedb but only has large page size (65536) machine at his hand

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.
• API changes are backward compatible.
• Schema or data changes are backward compatible.

[Copilot]

Pull Request Overview

This PR adds support for building GreptimeDB with large page size (65536) to accommodate customers who only have machines with large page sizes available for testing.

• Added a large-page-size boolean input parameter to the dev-build workflow
• Configured the build system to set JEMALLOC_SYS_WITH_LG_PAGE=16 environment variable when large page size builds are requested
• Propagated the parameter through the GitHub Actions workflow and build actions

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
Makefile	Added EXTRA_BUILD_ENVS variable and ASSEMBLED_EXTRA_BUILD_ENV to pass environment variables to docker build commands
.github/workflows/dev-build.yml	Added large-page-size workflow input parameter and passed it to build jobs
.github/actions/build-linux-artifacts/action.yml	Added large-page-size input and propagated it to build steps
.github/actions/build-greptime-binary/action.yml	Added logic to set JEMALLOC_SYS_WITH_LG_PAGE=16 environment variable based on large-page-size input

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.