Improve handling of generated style extensions for components with the same class name, different qualified name

[laurakelly]

I'm using Paris in a library with many modules. We have had an issue with naming collisions for components that have a different fully qualified name but the same class name.

They all get a style extension generated for them which are all in the same package (Paris), so in this situation there is a class name conflict.

I'm wondering if it's possible to change the code generation code for Paris to avoid this conflict.

[ngsilverman]

@laurakelly style extension classes purposefully all use the same package so that they result in the same import statement regardless of which or how many views are being styled. However the name of the file could be changed to include the qualified name of the corresponding class here:
https://github.com/airbnb/paris/blob/master/paris-processor/src/main/java/com/airbnb/paris/processor/writers/StyleExtensionsKotlinFile.kt#L35

At the moment the name of the file will be the same as the view, like MyView.kt. We could make it something like ComExampleApplicationMyView where MyView is in the com.example.application package.