[typescript-node] Fixes generation when parent contains TypeScript primitive

[fetis]

When the schema contains additionalProperties, the type value of it was transferred into the parent property of the model. This led to incorrect code generation, like this

        "additionalProperties": {
          "type": "boolean"
      }

...      

export class PizzaDto extends boolean {
...
}

This fix filters out the known TS primitives from the parent property.

Closes #14661

Mentioning the TypeScript committee:
@TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @topce @akehir @petejohansonxo @amakhrov @davidgamero @mkusaka @joscha

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[fetis]

any value comes when the schema has additionalProperties: true

[fetis]

I need help with CircleCI tests. The error looks disconnected from my changes

[macjohnny]

thanks for the fix

[macjohnny]

@fetis can you merge the most recent master branch?

[fetis]

@macjohnny updated from the master

[fetis]

@macjohnny any update? I see random failures on CI, but I cannot connect them with my changes

[macjohnny]

can you merge the master branch again? that one seems green for all CI workflows