This is a follow-up to #367, which enabled the API to store and update web_data. The format is a flattened hash, which is stored as a string in the database. That PR converted the hashes into strings with embedded newlines, which looks pretty, but was not intended, because historically this is not how the data has been stored. I'm not aware of newlines being problematic, but it's conceivable that, say, a regex somewhere might not work on a multiline string. This PR removes newlines from the stored web_data.
Use case
Various Production and non-vert pipelines use this API functionality to propagate web_data from the production DB to core DBs.
Benefits
Makes code fully consistent with previous functionality; avoids potential parsing problems.
Possible Drawbacks
None I'm aware of.
Testing
Have you added/modified unit tests to test the changes?
Yes, analysis.t
If so, do the tests pass/fail?
Pass
Have you run the entire test suite and no regression was detected?
Yes
