Published workflow disappears from Elsa Studio but remains in workflow-definitions API with isPublished: true, isLatest: false

[get-user.json](https://github.com/user-attachments/files/22166603/get-user.json)

## Bug Summary
When publishing a workflow definition (example attached) in a self-hosted Elsa Server (built from the Elsa.Server.Web reference setup), the workflow disappears from the Elsa Studio (elsaworkflows/elsa-studio-v3-5-0:latest) workflow definition list. However, the workflow is still visible via the workflow-definitions API (e.g., via Postman), with `isPublished: true` and `isLatest: false`. There are no other versions of the workflow (the /versions endpoint confirms this).

- Elsa.Server.Web based on v3.5.0, references as in the default repo, see Program.cs and package references below.
- Elsa Studio connects correctly; creating and saving a draft workflow works as expected.
- As soon as the workflow is published, it disappears from the Studio UI but is still returned by the API (isPublished: true, isLatest: false).
- There are no other versions (checked with /workflow-definitions/{id}/versions).
- This happens even if there were never any previous versions.

### Sample Workflow Definition (JSON)
```json

```

### Elsa Server Setup (Program.cs and packages)

### Expected Behavior
- Published workflow should remain visible in Elsa Studio if it is the only version and isPublished: true.

### Actual Behavior
- Published workflow disappears from Studio. API returns it with isPublished: true, isLatest: false. No other versions exist.

### Steps to Reproduce
1. Stand up Elsa.Server.Web 3.5.0 with default or attached Program.cs.
2. Create a workflow via Studio, save as draft (appears in Studio list).
3. Publish the workflow (now disappears from Studio, but isPublished: true, isLatest: false via API).
4. Check /workflow-definitions/{id}/versions: only one version exists.

### Additional Context
- This does not happen with Elsa Cloud.
- The workflow should be visible if it is published and the only version.
- Possibly Studio expects isLatest==true for listing published workflows, but this never occurs after publishing.
- See attachments and Program.cs for exact setup and reference versions used.

fyi: using the elsaworkflows/elsa-server-v3-5-0:latest instead of the "custom"-elsa web-server works fine. however, I copied basically all relevant files from here (including appsettings):
https://github.com/elsa-workflows/elsa-core/tree/main/src/apps/Elsa.Server.Web
i only removed python and some code which was unreachable with the basic setup:
useSignalR = false;
useMultitenancy = false;

### Environment
- Elsa.Server.Web 3.5.0
- Elsa Studio v3.5.0
- All references match Elsa repo defaults
- Docker and manual builds both tested

### Labels
bug, workflow tooling, elsa 3, Elsa Studio