[expo-in-app-purchases][android] added the ability to set obfuscatedAccountId, obfuscatedProfileId and isVrPurchaseFlow (#16670)

# Why

Many application which use iAP on Android requires the obfus

[expo-in-app-purchases][android] added the ability to set obfuscatedAccountId, obfuscatedProfileId and isVrPurchaseFlow (#16670)

# Why

Many application which use iAP on Android requires the obfuscatedAccountId and obfuscatedProfileId to be set. A subset of applications may need isVrPurchaseFlow, making that property available to library consumer is low effort.

# How

Simply, we just check if `obfuscatedAccountId`, `obfuscatedProfileId` or `isVrPurchaseFlow` is passed to the `purchaseItemAsync` method, if they exist we set them on the `BillingFlowParams.Builder`.

**Note:** there is a small caveat, that `obfuscatedAccountId` and `obfuscatedProfileId` both need to be passed unless the Google iAP dialog will show the following error: "Something went wrong on our end. Please try again." ��‍♂️ Types are built to enforce this, consumer is made to pass both, not just one.

# Test Plan

Tests will be carried out today in the Qeepsake application to verify these values are being passed through to the Google Play webhook.

# Checklist

- [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
- [x] This diff will work correctly for `expo build` (eg: updated `@expo/xdl`).
- [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).

show more ...