i1278: send RUN_RECEIVED msg to TEAM when submission is via pc2submit...

[clevengr]

Description of what the PR does

Adds an extra step to PacketHandler.runSubmission(...), which is the method invoked when a Run is submitted to the PC2 Server. The extra step is to check whether the submission came from a "proxy" (such as the Event Feeder client -- for example when the pc2submit Python script is used to submit a run) and if so to send a RunSubmissionConfirm packet to the actual team client (that is, to the account that invoked pc2submit).

This extra step is necessary because pc2submit makes submissions via the Event Feed client, and the packet handler for submissions doesn't send a RunSubmissionConfirm packets to proxy clients like the EF client -- the result being that clients such as the WTI never get a notification of the run submission when it occurs via an invocation of pc2submit. This in turn keeps the WTI from displaying runs which are "Pending".

Issue which the PR addresses

Fixes #1278

Environment in which the PR was developed

Windows 11, java version "1.8.0_271", Chrome Version 149.0.7827.103, and Cursor Version 3.14.7 w/ LLM Grok 4.7

Precise steps for testing the PR

1. Ensure you have Python installed on your machine (it is needed to run the pc2submit script).
2. Download and unzip the PR distribution (or build it yourself on your machine).
3. Start a PC2 Server loading the clics_sumithello contest.
4. Start a PC2 Admin and use the Times tab to start the contest running
5. Start a PC2 Event Feeder client, login as "ef1", and press the Start button to start the Event Feed webserver running.
   1. Verify on the EF console that the EF web server started.
6. Start a WTI Server running (you may need to unzip the projects>WebTeamInterface-1.2 zip file; then in the resulting folder enter the command ./bin/pc2wti at a command prompt).
   1. Verify on the WTI console that the WTI web server started
7. Open a clean browser and connect to the WTI server (typically, using http://localhost:8080)
8. Login as team1/team1.
9. Select Submit Problem, then select any problem, any language, and any (text) file and click Submit.
10. Verify that the WTI Runs screen, under Judgement, shows the submission as Pending.
11. Open a command prompt in the PC2 distribution folder and submit a program using the command

python ./bin/pc2submit --url https://localhost:50443 --problem A ./samps/src/hello.cpp

12. On the PC2 Admin, look at the Run Contest>Runs screen and verify that TWO runs are Queued_for_computer_judgement (one is the first one you submitted above via the WTI; the second is the one you submitted using pc2submit).
13. Look at the WTI Runs screen; verify that there are TWO runs, both showing "Pending" under "Judgement".
14. On the PC2 Admin Run Contest>Runs screen, select the first run (the one submitted via WTI), click Edit, change the Run Status to JUDGED, change the Judgement to any judgement, check the Notify Team checkbox, and click Update.
15. On the WTI Runs screen, verify that the run status changes to whatever judgement you assigned, and that there is still a second run showing "Pending".
16. On the PC2 Admin, select the second run (the one submitted using pc2submit), click Edit, change the run Status to New, and click Update.
17. Ensure the second run is still selected, then click Request Run then Execute Run.
18. After the run executes, close the resulting Test Results screen and then select either Accept Validator or select a different judgement and click Accept Selected. (Be sure the Notify Team checkbox is checked.)
19. On the WTI Runs screen, verify that the second run now has the judgement you assigned.

[johnbrvc]

See the question I have...

[johnbrvc]

What happens if this run was submitted via the shadow/RemoteRunSubmitter.submitRun() from shadow/RemoteEventFeedMonitor.run()? That is, PC2 is acting as a shadow? Where does that notification that was added wind up?