Change bannerComment property to use ESLint, since TSLint has been deprecated for quite a bit

[krishnagopinath]

Thank you for this wonderful project, @bcherny!

Since TSLint was deprecated in 2019, I wonder if it would make sense to update the bannerComment property's default to use eslint-disable instead of tslint:disable.

[dianjuar]

This is a need.

I'm on a project that uses eslint and each time that I generate a new schema I have to modify by hand the banner.

Feels quite bad, especially having a comment just below that tolds you DO NOT MODIFY IT BY HAND

[DaSchTour]

For the start there could also be both

[bcherny]

PRs welcome to add ESLint suppression in addition to the existing TSLint suppression.

[dianjuar]

@bcherny I would like to implement this feature.

@bcherny I don't know how do you manage the help-wanted tag, but I would like to be assigned to this issue.

[JoshuaKGoldberg]

Can we do away with TSLint altogether, please? TSLint's been deprecated since 2019 and hasn't received any updates for security fixes or new TypeScript syntax in years. A lot of folks get confused about the difference in terminology with tslint vs. lint vs. eslint.