OK, I think you got 2 different items confused.
First, the war-tracker. It turns out that Tomcat adds this file to an exploded WAR so that it can detect changes made to that WAR while Tomcat was not running:
https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/config/host.html
There was a bug detected in 2016, reported and fixed, per your bug URL. As long as you're running a version of Tomcat newer than the versions listed in that bug report, that shouldn't be a problem. The problem was indicated in the change log, but as a repaired problem. The change log appears in a separate webapp named "docs", and offhand, I'd think that the docs app came with your copy of Tomcat, but you should be able to delete it safely (and it's one less security weakness if you do).
I said that
applications should never update a deployed WAR, but of course, Tomcat can do whatever it likes. Note, however, that this feature is only applicable if Tomcat has an exploded WAR. Though since that's the default, it would be doing so.
Your second concern comes from the fact that the webapp is deployed under the context path "/AwardTracker_NJE/". The award tracker app has no direct connection or knowledge of what Tomcat's trying to do with "war-tracker", the similarity between names is purely incidental. The "404" errors you see in the log indicate an unresolvable URL, and that's just what happens when an improper URL is passed to a webapp, either badly capitalized/spelled, or because a component of the application didn't get installed.