Preconfigured decorators aliases

This feature is kind partial apply equivalent from functional programming paradigm.

It gives you an ability to create decorators that have some options binded,
like `@NullableField() === @Field({ nullable: true })`:

```ts
const NullableField = createDecoratorAlias(Field, { nullable: true });
const AbstractResolver = createDecoratorAlias(Resolver, { isAbstract: true });
const IntField = createDecoratorAlias(Field, type => Int);
```

This might help to avoid common boilerplate and also can be useful for other libraries integration purposes.

No files or tests are named. Start by examining the existing Field and Resolver decorators and the proposed createDecoratorAlias entry point; determine how aliases should bind options and how the IntField example differs. Done should support the NullableField, AbstractResolver, and IntField use cases without changing existing decorator behavior.

Written by the indexing model from the issue text.