Fix button opacity problem when saving personal details

[Beamanator]

cc @tgolen since you were also looking into this solution yesterday

Details

The problem was, as mentioned here, some rerendering or gestures made the Opacity animation stop before it finished. In that comment I show some console logs that indicate the Animation never finished, so in this fix I make sure the Undim animation will always finish. It's possible we'll need the same for Dim in the future, but that's not something we need to worry about right now.

One alternate solution I had was to try to check if the value of this.opacity was < 1 & if this.props.shouldDim was false, like this:

if ((prevProps.shouldDim || this.opacity < 1) && !this.props.shouldDim) {
    this.undim();
}

However this doesn't work because this.opacity is an Animated value - to get its value you have to do something hacky (see this SO)

So instead of doing something hacky, we now just make sure it fully undims (becomes fully visible) when needed.

Fixed Issues

$ #10230

Tests

1. Open Settings -> Profile
2. Edit your name or pronouns
3. Save changes
4. Edit again, verify that the "Save button" has full opacity - meaning it's fully visible, doesn't look disabled at all
5. Repeat steps 2 - 4 a few times, making sure the Save button always returns to full visibility after you start editing your details, and it becomes disabled (and isn't clickable) when the details have been saved & aren't edited

• Verify that no errors appear in the JS console

PR Review Checklist

Contributor (PR Author) Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • iOS / native
  • Android / native
  • iOS / Safari
  • Android / Chrome
  • MacOS / Chrome
  • MacOS / Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product was added in all src/languages/* files
  • I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • Any functional components have the displayName property
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

QA Steps

1. Open Settings -> Profile
2. Edit your name or pronouns
3. Save changes
4. Edit again, verify that the "Save button" has full opacity - meaning it's fully visible, doesn't look disabled at all
5. Repeat steps 2 - 4 a few times, making sure the Save button always returns to full visibility after you start editing your details, and it becomes disabled (and isn't clickable) when the details have been saved & aren't edited

• Verify that no errors appear in the JS console

Screenshots

Web

Screen.Recording.2022-08-03.at.1.04.18.PM.mov

Mobile Web

Screen.Recording.2022-08-03.at.1.21.17.PM.mov

Desktop

iOS

Screen.Recording.2022-08-03.at.1.44.13.PM.mov

Android

Screen.Recording.2022-08-03.at.1.51.48.PM.mov

[github-actions]

⚠️ ⚠️ Heads up! This pull request has the CP Staging label. ⚠️ ⚠️
Merging it will cause it to be immediately deployed to staging, even if the open StagingDeployCash deploy checklist is locked.

[arosiclair]

LGTM though I'll let @tgolen chime in since he was looking at this more closely

[Beamanator]

Merging since this fix is pretty useful, still interested in feedback from @tgolen if you have any :D

[OSBotify]

🚀 Cherry-picked to staging by @Beamanator in version: 1.1.88-4 🚀

platform	result
🤖 android 🤖	failure ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.