Consider adding require-atomic-updates when it becomes more stable

[manovotny]

As much as we want to include it, it's just too unstable right now and causes too many false positives right now.

• require-atomic-updates false positive eslint/eslint#11899
• require-atomic-updates complains about unrelated variable references eslint/eslint#11900
• require-atomic-updates reports false positive in finally block eslint/eslint#11954

[roboli]

It won't let me do this for example

`let action;

const withAction = async () => {
  if(!action) {
    action = await actions.getOne({ id });
  }
  return { action };
};`

Do you think is also due the above? Thanks.

[manovotny]

@roboli yep, that's exactly why I removed it from v5 after beta feedback.

I just released 5.0.0-beta.5, which no longer contains the rule.

[manovotny]

Updated original message. Two of three issues fixed! Progress, but still holding off on adoption for now.