fix: remove <any> from enum declaration

[RobbyUitbeijerse]

Hi there!

Currently the enum values generated through the typescript-node generator are typed as . They get outputted like so:

export enum TestEnum {
    Something = <any> 'something'
}

But there seems to be no apparent reason as to why is being used. Note that the last change to this line was 5 years ago, so there might have been a perfectly understandable reason why this was put in there at the time

However, with modern Typescript this leads to issues, as it isn't able to infer the enum value. For example, the following code leads to issues:

export enum TestEnum {
    Something = <any> 'something'
}

const foo = 'something'

foo === TestEnum.Something 

Attached below is an illustration of what is going on:

When the typing is removed, the enum gets processed correctly and string/enum comparison works as expected.

Let me know if I'm missing something here. Please note that other typescript generators that I've checked don't have the type in place. (typescript-axios for example)

[wing328]

can you please follow step3 in the PR checklist to update the samples so that CIs can verify the change?

@TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09) @macjohnny (2018/01) @topce (2018/10) @akehir (2019/07) @petejohansonxo (2019/11) @amakhrov (2020/02) @davidgamero (2022/03) @mkusaka (2022/04)