Squash annotations

[koperagen]

I thought, let's employ a bit shorted syntax to reduce noise
Maybe there are other annotations that can be squashed, i squashed only the most popular

[Jolanrensen]

I would try to follow/create a little style guide for all our annotations. I just submitted an issue for ktlint pinterest/ktlint#3212 for this, as it doesn't seem to know @[] notations.

You now create:

@[Deprecated(DEPRECATED_ACCESS_API) AccessApiOverload]
@Suppress("INAPPLICABLE_JVM_NAME")
@JvmName("frameColDataFrameKProperty")
public fun <C> AnyColumnGroupAccessor.frameCol...

I would recommend putting the @[] at the bottom. It looks a bit cleaner, in my opinion:
You now create:

@Suppress("INAPPLICABLE_JVM_NAME")
@JvmName("frameColDataFrameKProperty")
@[Deprecated(DEPRECATED_ACCESS_API) AccessApiOverload]
public fun <C> AnyColumnGroupAccessor.frameCol...

Also, we don't really honor an order. What about just lexicographically?

@JvmName("frameColDataFrameKProperty")
@Suppress("INAPPLICABLE_JVM_NAME")
@[AccessApiOverload Deprecated(DEPRECATED_ACCESS_API)]
public fun <C> AnyColumnGroupAccessor.frameCol...

Next, the plan is to "compact" multiple annotations that are often used together?

We could probably include the JvmName one then too:

@[AccessApiOverload Deprecated(DEPRECATED_ACCESS_API)]
@[JvmName("frameColDataFrameKProperty") Suppress("INAPPLICABLE_JVM_NAME")]
public fun <C> AnyColumnGroupAccessor.frameCol...

wdyt?

[AndreiKingsley]

@Jolanrensen to be honest, it doesn't look very pretty to me, however the idea of grouping annotations seems great!