chore: bump go, tools, deps and re-kres, satisfy linters

[utkuozdemir]

Bump everything.

[Copilot]

Pull Request Overview

Bump Go version, dependencies, tool versions, and update code to satisfy new linter checks.

• Added //nolint:embeddedstructfieldcheck comments on embedded dag.BaseNode fields
• Reordered struct fields in several modules
• Updated version constants, go.mod, Dockerfile syntax, Makefile, and CI workflows

Reviewed Changes

Copilot reviewed 19 out of 20 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
internal/project/js/build.go	Reordered meta and dag.BaseNode fields in Build
internal/project/common/release.go	Moved meta below dag.BaseNode in Release
internal/output/ghworkflow/types.go	Reordered Name and Schedule fields in workflow types
internal/config/constants.go	Bumped various image and tool version constants
go.mod	Updated Go version and bumped dependency versions
Dockerfile	Upgraded frontend image syntax and bun version

Comments suppressed due to low confidence (4)

internal/project/js/build.go:26

• The order of struct fields was changed by moving meta below dag.BaseNode. This alters the memory layout and may affect initialization or behavior—please confirm this reordering is intentional or revert to the original order.

	meta *meta.Options

internal/project/common/release.go:26

• Reordering the meta field below dag.BaseNode changes the struct layout. Verify that this change won't break serialization or upstream consumers.

	meta *meta.Options

internal/output/ghworkflow/types.go:14

• Moving the Name field changes the order of keys in generated YAML. Ensure this reordering won't break existing GitHub workflow expectations.

	Name        string            `yaml:"name"`

internal/output/ghworkflow/types.go:32

• [nitpick] Reordering Schedule within the On struct can change the sequence of fields in the output YAML—please confirm it's intentional.

	Schedule []Schedule `yaml:"schedule,omitempty"`

[utkuozdemir]

/m