Use NeDB to replace our own memory connector about loopback-next

[superkhau]

@bajtos Thoughts too?

[bajtos]

I don't mind either way. Here are two questions to consider:

• Will the complexity of writing nedb connector outweigh the cost of maintaining our existing memory connector?
• I personally find _id property a big ugly. IIRC, MongoDB has the same issue and we are somehow converting _id to id in our convertor. I guess we can do the same with nedb, but it's another extra complexity to take into our consideration.

[superkhau]

I'm going to close this as maintaining our own gives us more control, like Context for example. Will reopen if necessary to reduce issue count.