Fix Docker and CI builds

[philon-]

Description

This is a PR which attempts to address some issues with CI workflows

Related Issues

Changes Made

• Don't attempt publishing web for release-packages workflow
• Add explicit meshtastic/core deps for transport packages
• Change to workspace:* dependencies in monorepo packages
• Change dist folder pointer in Dockerfile
• Update pnpm-lock

Testing Done

Tested locally using ACT, some testing in my own fork.

Screenshots (if applicable)

Checklist

• Code follows project style guidelines
• Documentation has been updated or added
• Tests have been added or updated
• All i18n translation labels have been added (read
  CONTRIBUTING_I18N_DEVELOPER_GUIDE.md for more details)

[vercel]

@philon- is attempting to deploy a commit to the Meshtastic Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull Request Overview

This PR fixes Docker and CI build issues by updating the project to use a monorepo setup with proper workspace dependencies and updated build configurations.

• Standardizes package build configurations across all transport packages
• Updates dependency references to use workspace:* pattern for internal packages
• Adds proper vitest configuration for monorepo testing setup

Reviewed Changes

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

Show a summary per file

File	Description
vitest.config.ts	Root vitest config for monorepo test projects
packages/web/vitest.config.ts	Updated web package test config with corrected paths
packages/web/package.json	Changed transport dependencies to workspace references
packages/web/infra/Containerfile	Fixed Docker dist folder path
packages/transport-*/package.json	Added @meshtastic/core dependencies and standardized tsdown config
package.json	Added vitest dependency and test script
.github/workflows/*.yml	Updated CI workflows to use pnpm and skip web package in releases

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[danditomaso]

There was also an issue around the build.tar not being created when a release or pre-release is created, does this PR address this?

[philon-]

There was also an issue around the build.tar not being created when a release or pre-release is created, does this PR address this?

Yes... should. 😉

[danditomaso]

Looks really good!