Fix for records with prim namespace prefix

We're writing a search landing page that splits our local holdings and electronic results similar to what Villanova is doing: https://library.villanova.edu/Find/Resource/Results?lookfor=van+gogh&type=&search=allresources&submit=Find

When I attempted to search Primo Central I found that some records were not being parsed correctly due to being namespaced as <prim:record>.  This pull requests sends the original namespaces along with the raw_xml, then builds an xml document and removes the namespaces so it matches the expected structure of <record></record>.

I'm not tied to the way I implemented the fix so let me know if you'd like to see it done in a different manner or if the tests are lacking.