Lint Config: Support Passing Context thru to Rules

[wmccrthy]

This PR implements two next steps for lute lint's configuration system: rule context and rule-specific ignores.

Context is a table of globals and rule specific options, as configured by the user. For example, given a configuration of:

{
...,
	globals = {
		myGlobal = 1
	},
	rules = {
		myRule = {
			options = {
				myOption = 1
			}
		}
	}
}

we will the following context to each call of myRule:

{
	globals = {
		myGlobal = 1
	},
	options = {
		myOption = 1
	}
}

This enables rule authors to write logic w/ configurability in mind, and extend their analyses to use-cases beyond the default.

Rule-specific ignores extend the global-lint ignores (implemented in this PR), but are evaluated per-rule. This enables more granular ignore behavior, where we can effectively turn off rules for certain files / paths.

[skberkeley]

Suggested change

	lintConfig: types.LintConfig, -- will be used in follow-up PRs
	lintConfig: types.LintConfig,

[skberkeley]

we should do this at the lintPaths level, instead of redoing it for every file

[wmccrthy]

We can move some of the derivation out for sure, but we'll need to pass thru globals and rule configs to this to lintString regardless, since I assume this is the level at which we'll do things like:

• override violation severity w/ the configured severity
• not run rules according to rule-specific ignores

[skberkeley]

yeah sorry, i just meant we shouldn't do the computation of globals and options at this level