Ignore data-no-store-string-literals rule for native files

[aristath]

Description

Came up in a discussion with @gziolo after the comment on #31934 (comment)

Ignoring the rule for native files will prevent the next person from making the same mistake I did.

How has this been tested?

Running npm run lint-js no longer throws warnings for native files for the data-no-store-string-literals check.

Types of changes

Turned off the @wordpress/data-no-store-string-literals rule for native files in the .eslintrc.js file.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).

[gziolo]

Yes, let's do it. There is #29655 filed which should include a note to turn this flag on again when violations are fixed.