resolves #1327

In Angular 16, you can pass an object expression as an argument for the Input decorator.

This PR adds support for the following cases:

@Input({ required: <true|false> })
requiredInput: any;

@Input({ alias: 'some-alias' })
aliasedInput: any;

@Input({ required: <true|false>, alias: 'some-alias' })
requiredAndAliased: any;

Additional information:
Hi! I am a Storybook maintainer, and currently, we evaluate Angular 16 support in Storybook, which will be released in the first week of May. Now, Storybook relies heavily on Compodoc to extract type information. Passing an object expression to the Input decorator currently breaks completely because compodoc a) wrongly extracts the name property of the input (it always assumes that a StringLiteral is passed in as the only valid argument) and b) cannot handle object expressions as valid decorator arguments.

Further help needed:
I need help writing a unit test for the mentioned cases. I need some assistance to place a unit test into the right place.

PR opened against master instead of develop
I don't know how stable develop is and whether a soon-ish release of develop might be possible. Therefore, I've created the PR against master, hoping this fix might be released as a hotfix release.