Json db doesn't respect dbName option on field

[noam-honig]

Describe the bug
The dbName option of a field, works great in postgres and sql - but doesn't work when it comes to json db.
To Reproduce
Consider the following class:

@Entity("tasks", {
    allowApiCrud: true
})
export class Task {
    @Fields.uuid()
    id!: string;

    @Fields.string({dbName:'theTitle')
    title = '';

    @Fields.boolean()
    completed = false;
}

When the data is stored in the tasks.json file, the second field is stored as title and not theTitle

[
  {
    "id":"a",
    "title":"Task a"
  }
]

Expected behavior
it should be called theTitle in the json file:

[
  {
    "id":"a",
    "theTitle":"Task a"
  }
]

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[Informagier]

I believe, the underlying cause is the ArrayEntityDataProvider

remult/projects/core/src/data-providers/array-entity-data-provider.ts

Line 72 in 374cb31

translateFromJson(row: any) {

remult/projects/core/src/data-providers/array-entity-data-provider.ts

Line 79 in 374cb31

translateToJson(row: any) {

It just maps the column keys without checking the dbName

I will look deeper into it, when I have time :)

[Informagier]

Okay, sadly, I could not fix it and maybe these code snippets are unrelated to this bug

[noam-honig]

You're in the right place, you can take inspiration from the implementation of Mongo at:
https://github.com/remult/remult/blob/master/projects/core/remult-mongo.ts#L34