Fix Server Error Parsing

[garrettmflynn]

fix #544

Was excluding any strings after the second (or later) colon when parsing error messages from the server.

[rly]

Thanks! That seems to work. However, now it looks like <...> is not being escaped properly.

The error message should say:

Unable to identify the OpenEphys folder structure! Please check that your `folder_path` contains sub-folders of the following form: 'experiment<index>' -> 'recording<index>' -> 'continuous'.

but instead shows:

[garrettmflynn]

I can't replicate this exact issue since I don't have the same file. I'm not splitting on those <...>, so it's odd that they aren't showing up.

How large is this file? That would be the easiest way to make sure everything is caught.

[rly]

To replicate the issue, I think you will not need the file but should be able to do the following:

1. create a new temp folder name "temp"
2. create a new empty or nonsense file in that folder named "continuous.dat"
3. create a new conversion in NWB GUIDE and add the OpenEphysRecordingInterface
4. when asked "Will you locate your files programmatically?" select No
5. populate some subject details
6. on the Source Data page, for your subject, under OpenEphysRecordingInterface > Folder Path, select the file chooser and select the new "temp" folder
7. click Request Metadata Schema button to see error

[garrettmflynn]

Ah I see now. I was injecting the error into the HTML for formatting reasons, and <...> is interpreted as an invalid singleton HTML tag. I've replaced these with the proper character entities to render properly.

[rly]

Works on my end! Thanks!