fix: use turbo get instead of getEnforcing in native module

[ignaciosantise]

Description

getEnforcing was failing in a brand new expo project with new architecture enabled. Replaced getEnforcing with get in the native module spec

Type of change

• Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

Tested on sample dapp with new architecture enabled and on brand new expo project

Checklist

• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules