Back out "Add an op_lowering_disallow_list in fx splitter base class. (#82288)"

[wushirong]

Summary:
Revert since this breaks BC test
More context:
failing test
https://www.internalfb.com/.../fblearner/details/361780349/
issue report thread
https://fb.workplace.com/groups/2211200152361974/permalink/2303690223112966/

Test Plan: All unit test

Differential Revision: D38399966

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/82750
• ❔ Python docs are pending
• ❔ C++ docs are pending
• ❓Need help or want to give feedback on the CI? Visit our office hours

✅ No Failures (13 Pending)

As of commit 3529aa9 (more details on the Dr. CI page):

Expand to see more

---

💚 💚 Looks good so far! There are no failures yet. 💚 💚

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D38399966

[facebook-github-bot]

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here

[github-actions]

Hey @wushirong.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.