FCT2-19239: Display Egress workspace in activity log when connecting/…

[NeilFoubister]

…disconnecting.

[HasanCPS]

@NeilFoubister The 42703: column c.egress_workspace_name does not exist failures aren't a code bug, the test database is just behind the branch.

This branch adds EgressWorkspaceName to the CaseMetadata entity, which means EF now selects egress_workspace_name in every query that touches case_metadata. That's why tests with nothing to do with the new feature are failing as well.

The migration for the column (20260610101825_AddEgressWorkspaceNameToCaseMetadata) is in the branch, but nothing applies it automatically. The integration test fixture (IntegrationTestFixture.InitializeDbContext) connects straight to whatever CaseManagementDatastoreConnection points at and never calls Database.Migrate(). Migrations only get applied through the release pipeline scripts, so a migration that exists only on this branch won't be in the dev database yet.

Rather than applying the migration by hand every time this happens, I'd suggest having the fixture apply pending migrations itself. In IntegrationTestFixture.InitializeAsync, after the DbContext is created:

public async Task InitializeAsync()
{
    InitializeEgressClients();
    InitializeDdeiClient();
    InitializeDbContext();
    InitializeNetAppClient();

    if (DbContext != null)
    {
        await DbContext.Database.MigrateAsync();
    }
}

MigrateAsync is a no-op when the database is already up to date, so it only does work when a branch carries a new migration. That fixes this failure and stops the next migration from tripping the tests the same way.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[HasanCPS]

LGTM!