Fix - incremental setup dependency

[jordond]

Editing any composable makes Pose regenerate every preview in the module without its theme, warning PG024, until the next clean build.

getSymbolsWithAnnotation only returns symbols from KSP's dirty file set. Nothing in user source connects a composable to the config object. That edge only exists in the code Pose emits, as AppPose.Theme { ... }. So on any round that didn't touch the config file, the processor couldn't see it and took the no-config path.

Generated previews now declare the setup object's file as a Dependencies source alongside their own, which keeps it in the dirty set:

val sources = listOfNotNull(containingFile, setupFile).distinct()
Dependencies(aggregating = false, *sources.toTypedArray())

I tried aggregating = true first. It doesn't work: only declared sources land in the dirty set, so you regenerate more files and still lose the theme. Previews stay isolating and incremental cost is unchanged.

Parameter types, sealed subtypes and PreviewParameterProvider classes don't need the same treatment. They're all named in user source, so Kotlin already dirties the composable when they change. I reproduced both to check.

To reproduce: put @PoseSetup in its own file, build, add a comment to any @Pose composable, build again.

Note

I was going to add tests, but wanted to keep the diff only related to the fix.

Repro and tests needs two compilations and CompileHarness is one-shot, so covering it means a TestKit source set. I have that working on a branch if you want it as a follow-up.

[AkshayChordiya]

Great find and thank you so much for the fix, will merge it in!