tests: deploy tests

[doc-han]

Short Description

Adds integration tests for deploy/pull v1 & v2

Fixes #1270

Implementation Details

A more detailed breakdown of the changes, including motivations (if not provided in the issue).

QA Notes

List any considerations/cases/advice for testing/QA here.

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

• I have used Claude Code
• I have used another model
• I have not used AI

You can read more details in our
Responsible AI Policy

Release branch checklist

Delete this section if this is not a release PR.

If this IS a release branch:

• Run pnpm changeset version from root to bump versions
• Run pnpm install
• Commit the new version numbers
• Run pnpm changeset tag to generate tags
• Push tags git push --tags

Tags may need updating if commits come in after the tags are first generated.

[doc-han]

@josephjclark so the failing test here is the weird case. actually doesn't work as expected for me

[josephjclark]

Pushing some changes here:

1. I've added some assertions and made some small refactors to the v1 deploy
2. I've hit some really big problems with the test commands loading bad values from my environment. So I've added fixes around that.
3. I've restructured v1 pull tests a it - I basically want to test pull standalone. We used to have an older test on that but I've ripped it out. One test is still failing but I'll get to it tomorrow

[josephjclark]

I'm sure there's a bug in v1 where state files get written with workflow ids that aren't lower cased.

I keep seeing issues where my-workflow is written to state.json as My-Workflow, and that keeps causing tests to break.

I don't want to get involved in v1 code so I'm leaving this for now. I'll raise an issue if I can find a clear repro case.

EDIT: fixing the casing in the yaml files help this. I think tests were accidentally passing before because they were pointing to state files that didn't exist (a different bug which I've fixed)

[josephjclark]

Love the tests (and I've fixed the issues) but I can't merge this until the lightning mock API has been updated to not duplicate the version algorithm.

I expect I'll fix this on Friday

[doc-han]

Resolved. lightning mock now uses the same hashing as the projects package

[josephjclark]

Oh thank you @doc-han , that's super helpful!

[josephjclark]

Leaving this skipped because I think it's a real bug. I'm investigating that on another branch - but I want to merge the good stuff here into main