Remove un-needed "test:realsvc:run" scripts (#25356)

## Description

Remove un-needed "test:realsvc:run" scripts. Note that one of these
scripts still remains in
`packages/test/test-end-to-end-tests/package.json` which is actually
generic over its service, and that is referenced by
`packages/test/test-drivers/README.md` and
`packages/test/test-end-to-end-tests/README.md`

This change was made to address
#25292 (comment)

Author: CraigMacomber

packages/service-clients/end-to-end-tests/azure-client/package.json

@@ -31,7 +31,6 @@
 		"test:realsvc": "npm run test:realsvc:tinylicious",
 		"test:realsvc:azure": "cross-env FLUID_CLIENT=azure npm run test:realsvc:azure:run -- --driver=r11s --r11sEndpointName=frs",
 		"test:realsvc:azure:run": "mocha --recursive \"lib/test/**/*.spec.*js\" --exit --timeout 20000 --config src/test/.mocharc.cjs",
-		"test:realsvc:run": "mocha lib/test --config src/test/.mocharc.cjs",
 		"test:realsvc:tinylicious": "start-server-and-test start:tinylicious:test 7071 test:realsvc:tinylicious:run",
 		"test:realsvc:tinylicious:report": "npm run test:realsvc:tinylicious",
 		"test:realsvc:tinylicious:run": "npm run test:realsvc:azure:run -- --driver=t9s",

packages/service-clients/end-to-end-tests/odsp-client/package.json

@@ -29,7 +29,6 @@
 		"test:coverage": "c8 npm test",
 		"test:realsvc:odsp": "cross-env npm run test:realsvc:odsp:run -- --driver=odsp --odspEndpointName=odsp",
 		"test:realsvc:odsp:run": "mocha --recursive \"lib/test/**/*.spec.*js\" --exit --timeout 20000 --config src/test/.mocharc.cjs",
-		"test:realsvc:run": "mocha --recursive \"lib/test/**/*.spec.*js\"",
 		"test:realsvc:verbose": "cross-env FLUID_TEST_VERBOSE=1 npm run test:realsvc"
 	},
 	"c8": {

packages/test/test-drivers/README.md

@@ -43,12 +43,12 @@ The `function` syntax must be used for `this.skip()` to be available, arrow func
 
 Some drivers take a second bit of configuration besides the driver type, which is a specific "target environment",
 usually referred to as `<driverType>EndpointName`, e.g. `odspEndpointName` and `r11sEndpointName`.
-These are important to get right for the specific environment you're targetting, otherwise the test driver might
+These are important to get right for the specific environment you're targeting, otherwise the test driver might
 configure things in a way that the target environment doesn't expect, and you could see weird and unexpected
 errors when running tests.
 
 Usually you'll pass these as extra flags when running tests. E.g., to run our e2e tests against a routerlicious instance
-running locally in docker per our dev setup for it, you'll want to run:
+running locally in docker per our dev setup for it in `@fluid-private/test-end-to-end-tests` you'll want to run:
 
 ```bash
 <base command to kick-off tests> --driver=r11s --r11sEndpointName=docker