Remove internal ObserverMode mentions

[JayShortway]

This removes all internal mentions of the term "observer mode", except when still necessary to test deprecated APIs.

• Some mentions are replaced by the PurchasesAreCompletedBy enum.
• Most mentions are replaced by a finishTransactions boolean, as that is the relevant interpretation of PurchasesAreCompletedBy for most components.

[RevenueCat-Danger-Bot]

	1 Message
:book:	Size increase: 2.16 KB

Generated by :no_entry_sign: Danger

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 65.21739% with 8 lines in your changes missing coverage. Please review.

Project coverage is 83.17%. Comparing base (b8bae4a) to head (f3ef682).

Files	Patch %	Lines
...n/com/revenuecat/purchases/amazon/AmazonBilling.kt	38.46%	5 Missing and 3 partials :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1710 +/- ## ======================================= Coverage 83.16% 83.17% ======================================= Files 223 223 Lines 7593 7596 +3 Branches 1074 1075 +1 ======================================= + Hits 6315 6318 +3 Misses 854 854 Partials 424 424 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[JayShortway]

How deep do we want to go with PurchasesAreCompletedBy? In my opinion, at some point components just need to know the relevant interpretation of it, without knowing all enum cases. For most components, that means knowing whether to finish transactions or not.

In practice this means I added PurchasesAreCompletedBy to the AppConfig constructor, but not to anything "below" that.

What are your thoughts?

[JayShortway]

We could opt to rename finishTransactions to something like completePurchases or finishPurchases to

• be more consistent (in wording) with PurchasesAreCompletedBy,
• less Apple-y, and
• more platform-agnostic,

but I don't feel strongly either way.

Thoughts?