refactor(express): split pingExpress into v1 and v2

[rishikeshdadam136]

Ticket: WCI-188

Context - https://bitgo.slack.com/archives/C057BHBRG4B/p1764020095794829?thread_ts=1764018507.602879&cid=C057BHBRG4B

The API behavior is not changing. We are splitting the combined v[12] route into two separate V1 and V2 routes, so both will continue to work and clients will not be affected.

[linear]

WCI-188 split pingExpress endpoint into v1 and v2 typed routes

[mrdanish26]

handlePingExpress is wired to both express.v1.pingexpress and express.pingexpress, but the parameter type only mentions express.pingexpress. Update to ExpressApiRouteRequest<'express.v1.pingexpress' | 'express.pingexpress', 'get'> so the type matches both registrations.

[rishikeshdadam136]

Added it

[mrdanish26]

Update comments so it matches the split

[mrdanish26]

Add a minimal test that both GET /api/v1/pingexpress and GET /api/v2/pingexpress resolve and return the expected payload

[lokesh-bitgo]

Looks good

[vmccarty]

Suggested change

	* Ping BitGo Express
	*
	* @operationId express.pingExpress
	* @tag express
	* Ping bitgo express to ensure that it is still running. Unlike /ping, this does not try connecting to bitgo.com.
	*
	* @operationId express.pingexpress
	* @tag Express
	* @public
	*/
	export const GetPingExpress = httpRoute({
	path: '/api/v[12]/pingexpress',
	export const GetV2PingExpress = httpRoute({
	path: '/api/v2/pingexpress',
	* Ping BitGo Express
	*
	* Ping BitGo Express to ensure that it's still running. Unlike [Ping](/reference/expressping), this endpoint doesn't connect to bitgo.com.
	*
	* @operationId express.pingexpress
	* @tag Express
	* @public
	*/
	export const GetV2PingExpress = httpRoute({
	path: '/api/v2/pingexpress',

I'm still not sure how does this endpoint differs from /api/v2/ping that we currently instruct clients to use. How does it tell if Express is running?

[rishikeshdadam136]

/api/v2/ping checks if both Express and BitGo servers are reachable — if BitGo is down, it fails even though Express is fine.

/api/v2/pingexpress only checks if Express itself is running — it never contacts BitGo, so it always returns 200 as long as the Express process is alive.

So when pingexpress returns 200 { "status": "express server is ok!" }, that itself is the proof — the fact that the request was received and responded to means Express is alive and handling requests.