Merge remote-tracking branch

'origin/GP-6228_d-millar_protobuf_docs--SQUASHED' (Closes #8774)

Ghidra/Debug/Debugger-agent-dbgeng/src/main/help/help/topics/dbgeng/dbgeng.html

@@ -48,7 +48,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install pybag protobuf==3.20.3
+python3 -m pip install pybag protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

Ghidra/Debug/Debugger-agent-gdb/src/main/help/help/topics/gdb/gdb.html

@@ -38,7 +38,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install psutil protobuf==3.20.3
+python3 -m pip install psutil protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

Ghidra/Debug/Debugger-agent-lldb/src/main/help/help/topics/lldb/lldb.html

@@ -38,7 +38,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install psutil protobuf==3.20.3
+python3 -m pip install psutil protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>

Ghidra/Debug/Debugger-rmi-trace/DEVNOTES.txt

@@ -117,8 +117,6 @@ That said, for unit testing, I've had to incorporate package installation as a @
 There's probably a better way, and that way may also help with out-of-the-box support.
 Something like setting PYTHON_PATH before invoking the debugger?
 There's still the issue of installing protobuf, though.
-And the version we use is not the latest, which may put users who already have protobuf in dependency hell.
-We use version 3.20, while the latest is 4.something.
 According to protobuf docs, major versions are not guaranteed backward compatible.
 To upgrade, we'd also have to upgrade the Java side.
 

Ghidra/Debug/Debugger-rmi-trace/src/main/help/help/topics/TraceRmiLauncherServicePlugin/TraceRmiLauncherServicePlugin.html

@@ -134,7 +134,7 @@
     <UL style="list-style-type: none">
       <LI>
 <PRE>
-python3 -m pip install protobuf==3.20.3
+python3 -m pip install protobuf>=3.20.3
 </PRE>
       </LI>
     </UL>