`hardenIntrinsics()` twice emits ses_already_locked_down

[leotm]

Describe the bug

Calling hardenIntrinsics() twice unknowingly, emits SES_ALREADY_LOCKED_DOWN

which isn't immediately clear it's because we're repairing twice

endo/packages/ses/src/lockdown-shim.js

Line 24 in bd96489

const hardenIntrinsics = repairIntrinsics(options);

(also depending on the React Native version the stack trace may not be clear)

• feat: @lavamoat/react-native-lockdown LavaMoat/LavaMoat#1438 (comment)

ideally we should emit either

1 SES_ALREADY_REPAIRED or SES_ALREADY_HARDENED (similar original behaviour)
2 ignore subsequent calls to hardenIntrinsics()

Steps to reproduce

Call hardenIntrinsics() more than once

Platform environment

Additional context

Screenshots