fix: Use FQCN to avoid collisions in PackageList.java

[riteshshukla04]

Summary:

When two different React Native libraries export a package class with the same name but in different namespaces, the generated PackageList.java causes a compilation error due to ambiguous class references.

The current autolinking generates:

import com.pikachu.NativeStorage;
import com.snowfox.NativeStorage;  // ❌ Compile error: NativeStorage is already defined

public ArrayList<ReactPackage> getPackages() {
    return new ArrayList<>(Arrays.<ReactPackage>asList(
        new MainReactPackage(mConfig),
        new NativeStorage(),  // ❌ Ambiguous reference
        new NativeStorage()   // ❌ Ambiguous reference
    ));
}

Solution:-
Use fully qualified class names (FQCN) instead of imports:

// No imports needed
public ArrayList<ReactPackage> getPackages() {
    return new ArrayList<>(Arrays.<ReactPackage>asList(
        new MainReactPackage(mConfig),
        // pikachu-storage
        new com.pikachu.NativeStorage(),
        // snowfox-storage
        new com.snowfox.NativeStorage()
    ));
}

Changelog:

[ANDROID][FIXED]- Use FQCN to avoid collisions

Test Plan:

Updated test.
Also tested on my app and RN tester

CI will tell if build fails

[cortinico]

This works, thanks for sending it over 👍

[riteshshukla04]

@cortinico do you think we should do a change in react native cli config for this or this works?

[cortinico]

Nope this is sufficient, we don't need a CLI PR

[meta-codesync]

@cortinico has imported this pull request. If you are a Meta employee, you can view this in D88157961.

[cortinico]

Can you just remove this line + remove the {{ packageImports }} from the template?

[riteshshukla04]

Done @cortinico . Thanks for pointing out