Opt-in feature to restart ANCM on 500.31 error

There are many times when shared hosting environments hit scnearios where they deploy a new version of the dotnet runtime and apps restart during that time. In that timeframe, apps may hit a 500.31 error because the entire dotnet framework isn't placed yet.

We recently added a feature to ANCM which makes it restart after hitting a startup timeout failure. We can do the same thing for error pages that include a response code of 500.31. We can also add a 60 second timeout before restart to avoid rapid failure (app starting too many times in a certain time frame) and CPU usage.