Switch usages of toAnnotationSpecFixed() to toAnnotationSpec()

[wbonnefond]

After updating our Android project from Kotlin 2.1.20 to 2.2.0 we started seeing compilation errors due to missing imports in some bindings generated by auto-dagger.

After debugging we found that .toAnnotationSpecFixed() was not pulling the fully qualified name. Switching this to Kotlin Poet's .toAnnotationSpec() allowed it to get the fully qualified name.

Before:

After:

[ansman]

@wbonnefond thanks for this! Looks great, but do you mind adding test that validates this?

[wbonnefond]

@ansman I added a test for the specific case that caused issues for us. I also updated existing tests which now are generated with value parameter name which I don't think should cause any issues since it's only on the generated code

The only change that I am concerned about is the need to change from @get:Named to @Named otherwise I saw the following errors:

  e: file:///var/folders/7t/1rj0m6gd72lgvl1fzt3brn0m0000gp/T/junit-5518362231190188529/auto_initialize/binding.qualified/ksp/ksp/sources/kotlin/tests/auto_initialize/binding/qualified/AutoInitializeBindingModule.kt:23:42 '@get:' annotations can only be applied to property declarations.
  e: file:///var/folders/7t/1rj0m6gd72lgvl1fzt3brn0m0000gp/T/junit-5518362231190188529/auto_initialize/binding.qualified/ksp/ksp/sources/kotlin/tests/auto_initialize/binding/qualified/AutoInitializeBindingModule.kt:23:42 This annotation is not applicable to target 'value parameter' and use-site target '@get'. Applicable targets: class, annotation class, property, field, local variable, value parameter, constructor, function, getter, setter, backing field, expression