[lint] use new merge-base-with feature in lintrunner ci

[suo]

Stack from ghstack:

• -> [lint] use new merge-base-with feature in lintrunner ci #75816
• [lint] add back some omitted clangtidy folders #75814
• [ci] fix make setup_lint #75804
• [ci] use lintrunner in CI #68460

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/75816
• 📄  Preview Python docs built from this PR
• 📄  Preview C++ docs built from this PR
• ❓Need help or want to give feedback on the CI? Visit our office hours

💊 CI failures summary and remediations

As of commit 12e0f3f (more details on the Dr. CI page):

---

💚 💚 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.

[seemethere]

Would probably be good to link the PR / commit that enabled this feature in lintrunner, just for reference

[suo]

for future peeps: suo/lintrunner@1a033ab

[suo]

@pytorchbot merge this

[github-actions]

Hey @suo.
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.