Rename .jsx files to .js and vice versa

[nbhargava]

@roryabraham will you please review this?

Optimistically, in making changes to the Expensify.cash desktop app, I want to avoid making webpack changes that require being able to parse JSX. expensify-common is not built or packed, so the imports that trace to it are made without any modifications. When the electron app tries to drive through the tree of pre-existing imports, it gets to a JSX file that causes problems.

Right now CONST.jsx is the main offender, but I figure it's worth switching some of the others. It is worth noting that there are still lint errors, but those seem to be independent of the changes I made. Mine just elucidate them.

Fixed Issues

N/A

Tests

1. What unit/integration tests cover your change? What autoQA tests cover your change?

Ran npm lint and saw no issues that were newly caused by renaming.

1. What tests did you perform that validates your changed worked?

Ran npm lint and saw no issues that were newly caused by renaming.

QA

1. What does QA need to do to validate your changes?
2. What areas to they need to test for regressions?

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[nbhargava]

I have read the CLA Document and I hereby sign the CLA

[roryabraham]

@nbhargava Is this PR still going to be necessary? I read your comment here and it led me to think you might not need to do this anymore?

[nbhargava]

Yeah probably not. Closing now.