feat: lb3 migration tests for models customized with db metadata

[deepakrkris]

satisfies: #3810

Checklist

👉 Read and sign the CLA (Contributor License Agreement) 👈

• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

[dhmlau]

@deepakrkris, there's error in npm run lint. Could you please run npm run lint:fix to see if it resolves the problem? Thanks.

[jannyHou]

+1 For fixing the lint error.

Otherwise LGTM 👍

[agnes512]

LGTM 👍

[derdeka]

@deepakrkris I'm just wondering why a string and not an object passed here. Why is this not like this?:

{
  type: `'string'`,
  tsType: 'string',
  length: 25,
  postgresql: {
    columnName: 'name',
    dataType: 'character varying',
    dataLength: 25,
    dataPrecision: null,
    dataScale: null,
    nullable: 'YES'
  },
},

[deepakrkris]

@derdeka thanks for the review. The unit test is for the function importLb3ModelDefinition it returns json values as strings. But the template generator takes care of converting into json objects.