RemotePingPong: don't let permission issues crash benchmark

[Aaronontheweb]

Changes

While trying to run RemotePingPong on our Raspberry Pi units in the test lab this evening, I kept running into permissions issues due to us trying to attempt process priority elevation. Decided to do what Benchmark.NET does and just log a warning and run without elevating the priority if that's going to be an issue for the runtime.

Checklist

For significant changes, please ensure that the following have been completed (delete if not relevant):

• This change follows the Akka.NET API Compatibility Guidelines.
• This change follows the Akka.NET Wire Compatibility Guidelines.

[Aaronontheweb]

Going to check to see if any of the other non-BDN benchmarks have this issue; I don't believe they do.

[Aaronontheweb]

Attempted to elevate process priority, but failed due to Permission denied - carrying on at normal process priority.
OSVersion:                         Unix 6.8.0.76060800
ProcessorCount:                    16
ClockSpeed:                        0 MHZ
Actor Count:                       32
Messages sent/received per client: 200000  (2e5)
Is Server GC:                      True
Thread count:                      43

Num clients, Total [msg], Msgs/sec, Total [ms], Start Threads, End Threads
         1,  200000,    129450,    1545.26,            43,              69
         5, 1000000,    240732,    4154.83,            77,              89
        10, 2000000,    517331,    3866.70,            97,              97
        15, 3000000,    416899,    7196.18,           105,              97
        20, 4000000,    519077,    7706.38,           105,              97
        25, 5000000,    536769,    9315.84,           105,              89

That's what I hope to see when we run into this issue - that little warning at the top.

[Aaronontheweb]

Whoops, sorry about the commit email looking funny - apparently my tailscale credentials got picked up instead of my gh login. That's also why my GPG signing failed. Whoops.