Chore: Optimizes adding Linter methods (fixes #9000)

[seandenison26]

What is the purpose of this pull request? (put an "X" next to item)
[X] Other, please explain: Chore, Optimized adding SouceCode object methods to the Linter prototype.

What changes did you make? (Give an overview)
I refactored linter.js to add the SourceCode object methods to the Linter prototype utilizing Object.defineProperties(). This allows any future methods to have more than five arguments as well as makes the new Linter.prototype properties non-enumerable.

Is there anything you'd like reviewers to focus on?

This should have been implemented exactly as requested in issue #9000 and all tests pass. Not sure what should be focussed on other than that.

[eslintbot]

Thanks for the pull request, @seandenison26! I took a look to make sure it's ready for merging and found some changes are needed:

• The commit summary must be 72 characters or shorter. Please check out our guide for how to properly format your commit summary and update it on this pull request.

Can you please update the pull request to address these?

(More information can be found in our pull request guide.)

[eslintbot]

Thanks for the pull request, @seandenison26! I took a look to make sure it's ready for merging and found some changes are needed:

• The commit summary must be 72 characters or shorter. Please check out our guide for how to properly format your commit summary and update it on this pull request.

Can you please update the pull request to address these?

(More information can be found in our pull request guide.)

[eslintbot]

LGTM

[platinumazure]

LGTM, thanks for contributing!

[platinumazure]

Note to merger: Change suffix from (fixes: 9000) to (fixes #9000) on merge.

[seandenison26]

Note to merger: Change suffix from (fixes: 9000) to (fixes #9000) on merge.

@platinumazure Does that mean I'll need to change the commit message?

[platinumazure]

@seandenison26 Actually your commit messages are fine, but GitHub's online pull request merge interface uses the PR title as the default suggested message, so I wanted to call it out to mergers in case someone was quick. (We do squash commits on merge, so the merge basically generates a new commit message based on the PR title unless we change it while merging.)

If you like, you can edit your PR title to help avoid this. But I was trying to avoid making you do extra work 😄

EDIT: Oh wait, I can change the PR title for you. Hope it's okay that I just went ahead and did that. Thanks!

[not-an-aardvark]

Looks good to me. Thanks for contributing!