Clean up JSON validation error handling

The recent schema changes broke our json error handling optimizations.

We thought about leaving them out completely for the validation but errors like:
In scope unmanaged_files: The property '#/0/type/0/1/2/3/type/4/5/type/6/type/7/8/9/10/11/type/12/17/18/19/20/21/22/23/24/25/26/27/28/29/type/30/31/33/34/35/36/37/38/39/40/41/42/43/44/45/46/47/48/49/476/477/478/479/480/481/482/483/484/485/486/487/488/489/490/491/492/493/494/495/496/497/498/499/500/501/504/type/505/type/506/type/507/type/508/type/509/510/511/512/513/514/515/516/517/518/519/520/type/582/583/type/584/type/585/type/586/type/587/type/588/type/589/590/type/591/type/592/593/594/595/type/596/type/597/598/type/599/type/600/type/601/type/602/603/604/605/606/607/608/609/610/611/612/804/805/806/807/808/809/810/811/812/813/814/815/816/817/818/819/820/821/822/823/824/825/826/827/828/829/830/831/832/833/834/835/836/837/838/839/840/841/842/843/844/845/846/847/848/849/850/851/852/853/854/855/856/857/858/859/860/861/862/863/864/865/866/867/868/869/870/871/872/873/874/875/876/877/878/879/880/881/882/883/884/885/886/887/888/889/890/891/892/893/894/895/896/897/898/899/900/901/902/903/904/905/906/907/908/909/910/911/912/913/914/915/916/917/918/919/920/921/922/923/924/925/926/927/928/929/930/931/932/933/934/935/936/937/938/939/940/941/942/943/944/945/946/947' of type Array did not match any of the required schemas.

are unacceptable so we created a dedicated method to clean up these messages.