feat(ci): Add e2e tests against latest docker images

[Copilot]

Merge PR #22576 with Latest Main - COMPLETED ✅

This PR successfully recreates all changes from PR #22576 (feat(ci): Add e2e tests against latest docker images) merged with the latest main branch.

Original PR Information

• Original PR: feat(ci): Add e2e tests against latest docker images #22576 by @alexvy86
• Title: feat(ci): Add e2e tests against latest docker images
• Status: Closed without merge
• Purpose: Add e2e tests against local routerlicious docker environment with latest server images

Changes Successfully Applied

• ✅ Update server/docker-compose.yml - Add nginx proxy, update image tags, change ports to expose
• ✅ Update server/routerlicious/docker-compose.yml - Add platform spec, update image tags to use variables
• ✅ Update server/routerlicious/packages/routerlicious/config/config.json - Enable whole summary upload
• ✅ Update tools/pipelines/templates/include-test-real-service.yml - Add preSteps and checkout parameters
• ✅ Update tools/pipelines/test-real-service.yml - Add new e2e docker test stage with server pipeline resources
• ✅ Address PR feedback - Remove volume mounts, fix checkout logic, add FLUID_LOGGER_PROPS
• ✅ Simplify pipeline checkout logic - Eliminate ffPipelineHostPath variable

Summary

All changes from PR #22576 have been successfully applied to the latest main branch (commit 46e6dce). The changes add:

• New nginx proxy configuration for docker environment
• Split image tags for historian, gitrest, and gitssh
• Enabled whole summary upload by default in docker config
• New CI pipeline stage for e2e tests against docker with server pipeline resource dependencies
• Simplified template with consistent directory structure (ff_pipeline_host at root, FluidFramework in subdirectory when needed)

Statistics: 5 files changed, 117 additions(+), 20 deletions(-)

Original prompt

Take the contents of @microsoft/FluidFramework/pull/22576 and merge the latest main, then open a fresh PR.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[tylerbutler]

/azp run Build - protocol-definitions,Build - test-tools,server-gitrest,server-gitssh,server-historian,server-routerlicious,Build - client packages,repo-policy-check

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[tylerbutler]

/azp run Build - api-markdown-documenter,Build - benchmark-tool,Build - build-common,Build - build-tools,Build - common-utils,Build - eslint-config-fluid,Build - eslint-plugin-fluid

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[tylerbutler]

@copilot Address the PR feedback.

[tylerbutler]

@copilot simplify the pipeline by always leaving ff_pipeline_host at the root ($(Build.SourcesDirectory)) and only checking out the FluidFramework repo as a subdirectory when needed. This would allow you to reference $(Build.SourcesDirectory) directly for all test host actions and use a sourcePath variable only when you need files from the FluidFramework repo (like the docker-compose.yml file), eliminating the need for ffPipelineHostPath and improving maintainability.

[Copilot]

@copilot simplify the pipeline by always leaving ff_pipeline_host at the root ($(Build.SourcesDirectory)) and only checking out the FluidFramework repo as a subdirectory when needed. This would allow ...

Simplified the pipeline checkout logic. Now ff_pipeline_host always stays at $(Build.SourcesDirectory) root, and FluidFramework checks out to a subdirectory (FluidFramework/) when needed via the checkout parameter. Eliminated the ffPipelineHostPath variable entirely - all paths now reference $(Build.SourcesDirectory) directly. This improves maintainability and consistency. Commit: bb2b53d