rm protoc cmd from pom.xml

[cicoyle]

Locally I have a diff protoc version. That results in a crazy bad error. To not use a developers local protoc Im removing it so cmds like mvn clean install will run without error.

I believe it fixes this issue or is at least a very similar err. See the err in the attached file.
protoc-issue.txt

Also noticed CI throwing:

Run ./mvnw compile -B -q
protoc-jar: executing: [protoc, --version]
protoc-jar: caught exception, retrying: java.io.IOException: Cannot run program "protoc": error=2, No such file or directory
protoc-jar: executing: [protoc, --version]
protoc-jar: caught exception, retrying: java.io.IOException: Cannot run program "protoc": error=2, No such file or directory
protoc-jar: executing: [protoc, --version]
protoc-jar: executing: [/tmp/protoc18031117828517050527.exe, --version]
libprotoc 25.5

[artur-ciocanu]

LGTM, does this mean that the Maven plugin will use its internal protoc version?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.70%. Comparing base (d759c53) to head (76a6d0d).
⚠️ Report is 200 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1498      +/-   ##
============================================
+ Coverage     76.91%   78.70%   +1.78%     
- Complexity     1592     1918     +326     
============================================
  Files           145      237      +92     
  Lines          4843     5926    +1083     
  Branches        562      610      +48     
============================================
+ Hits           3725     4664     +939     
- Misses          821      939     +118     
- Partials        297      323      +26     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.