[Paywalls V2] Makes TextComponent public

[JayShortway]

Public

This makes the TextComponent type, and all types it references, public. This allows us to use these types from revenuecatui. Note that they are still marked as @InternalRevenueCatAPI, so using them requires explicit opt-in. I still kept constructors internal for now. Will open things up more as we need it.

Data classes

We decided a while back that we don't want to use data classes in our public API, because they increase the API surface substantially (with copy() and componentN() functions), and are hard to evolve in a binary-compatible way.

However, having property-based equals() and hashCode() (and toString()) functions is still highly desirable. While these can be generated in Android Studio (CMD + N), the extra boilerplate adds substantial cognitive load when reading.

For this reason, this PR adds a compiler plugin called Poko, which generates these functions for us. It seems to be well maintained. This gives us the benefits of these functions, without the drawbacks of boilerplate. Let me know what you think.

[codecov]

Codecov Report

Attention: Patch coverage is 40.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 81.89%. Comparing base (a5375dc) to head (1f697fd).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...chases/paywalls/components/properties/ColorInfo.kt	16.66%	0 Missing and 5 partials ⚠️
...t/purchases/paywalls/components/properties/Size.kt	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1939   +/-   ##
=======================================
  Coverage   81.89%   81.89%           
=======================================
  Files         260      260           
  Lines        8449     8449           
  Branches     1226     1226           
=======================================
  Hits         6919     6919           
  Misses       1032     1032           
  Partials      498      498           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vegaro]

do these need the internal as well? I think it will be implicit

[JayShortway]

You used to be able to still call members of a non-public companion object from Java, but I think that had to do with private companion objects and not internal ones.

However, marking the fields as internal is not sufficient either to hide it from Java completely, as internal things become public, albeit with mangled names. (This became getDefault$purchases_defaultsRelease().)

I experimented some more and went with your earlier suggestion of using @JvmSynthetic (94003a4). This achieves the goal of hiding these fields from Java completely. Thanks for making me double check this!

[joshdholtz]

This looks good to me 🤷‍♂️