Update JSP Logic to Avoid Race Condition Regarding trackDependencies

[volosied]

After #17532, it was discovered that JSP may not always update the dependentsList properly when JSP handles concurrent requests. This means dependents are not tracked, and the JSP fails to updated when any changes occur to those include JSPs.

• Occurs when trackDependencies is true.
• Two simultaneous requests come in to the same jsp with after the server starts up.
  • First request comes in, the page is translated/compiled, and classloaderCreated is set as true within it’s synchronous block.
  • Second requests comes in just after the first request leaves the synchronous block. and then classloaderCreated is to to false.
• The class object containing this variable is a the same for the two requests so classloaderCreated also changes for the first request.
  classloaderCreated needs to be true for the check within loadClassInformation as that’s where the dependentsList is populated. If it’s not, then future requests to that page won’t check if the dependents are outdated (since it’s empty).

Scenarios where this can occur:

• Large Enough JSP. Code is synchronized, and the translation/compilation take a while, This creates a backlog of requests waiting to go into that sync block. When the first request leaves, the next comes comes in and sets classloaderCreated back to false. Then that first request, fails to add dependents. Then dependencies are not tracked.
• High Load ( Might not be ideal to update the JSP during this time)