revive: convert hard coded excludes into default exclude patterns

[ldez]

Fix #1937

The default behavior is still the same, but the PR allows users to use exported and package-comments rules.

[bombsimon]

Change LGTM but maybe we should follow up on #456, I se no reason excluding this by default, seems like old legacy because it was excluded for golint way back.

[ldez]

As revive has been introduced in v1.37, I think we need to keep the excludes for backward compatibility.

[bombsimon]

As revive has been introduced in v1.37, I think we need to keep the excludes for backward compatibility.

Yeah I get the idea but a bunch of linters has been updated with breaking changes (new lints etc) without us bumping major version. I have a hart time seeing us ever going to 2.0. But I guess you'll just have to not use --enable-defaults if you want these kind of warnings even though they're (as the issue states) the recommended way in Effective Go.