Treat linefeeds (\n, etc.) as invalid for collection (and database?) names

I was using node client

insertOne()

I accidentally called my collection "\n\ngamestatequests" 

a new collection as born which created me hrs of voodoo bug and undermined my confidence in the product...

I reported that the atlas site correctly listed my collection and the documents in it... 

but the mongo shell did not. 

had to go to a lot of extremes to figure this out... because even the sell don't render line feed characters in a database name.