Remote Staging validates incorrect groupID when publishing.

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, Master
• Fix Version/s: 7.0.0 DXP FP51, 7.0.0 DXP SP9, 7.0.X, 7.1.X, Master
• Component/s: Content Publishing > Staging
• Labels:
  • 7.1-could
  • ee-ts
  • liferay-dxp-70-sp9
  • liferay-fixpack-de-51-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Story Points: 1
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/60226

Reproduction Steps:

1. Start DXP with remote staging properties set for three different bundles (bundles #1, #2, and #3).
2. Create a site in each bundle (Site #1 in Bundle #1 and so on). Make sure that in Site #3, no siteIDs match the siteID of Site #2. For example: 
   Site #1 - Staging Site on localhost:8080 - Site ID 31342
   Site #2 - Remote Site on localhost:7080 - Site ID 31320
   Site #3 - Remote Site on localhost:9080 - Site ID 31338
3.  Setup remote staging between Site #1 and Site #2, with Site #1 as the staging site and Site #2 as the remote live site.
4. Create a publish template and under "Remote Live Connection Settings" change the value to the siteID of Site #3.
5. Publish using that template.

Expected Result: Contents of Site #1 are published to Site #3.

Actual Result: Publication fails. Error below is shown (the site ID is whatever site ID was setup as the original remote live site):

Your request failed to complete.
No site exists on the remote server with site ID 31320.