Add unescape to getAllType function

[PTR-inc]

This is used in the recode encrypted fields function

Some db functions have the un/escape in the function, but not all. For some it is done in app after the get.

I would propose to move it to the db functions instead of having to not forget it at the application level. I haven't checked all functions, but the GetAll function also doesn't do the unescaping for you.

@si458 What do you think?

[PTR-inc]

The recode function didn't work properly because of the missing unescape in the getalltype function. That triggered this.

[PTR-inc]

@si458 I think a full check on the mongo/nedb un/escape db functions is necessary to do this properly.

[PTR-inc]

@si458 Checked some of the functions used throughout the application for the different (un)escapes, here for example is the specific acebase db escapes, beside the nedb escapes. The only escape needed for mongo (v3.6 onward) is that a field must not start with a '$'.
Searching for 'unescape' in the source finds f.e. here and others, which, if forgotten in new functions, could lead to the bug fixed with this PR for the recode function. It would at least be safer to put all the (un)escaping in the db functions, I think.

Is it an idea to eliminate the need for escapes at all by generating the identifiers with something like crypto.randomUUID() or the UUID package?

That would remove a lot of overhead, room for mistakes and make it future-proof and more db agnostic.
What are your thoughts?