Add `skip_nolint` and `skip_nolint_exclude` attributes to nogo rule

Feature Request: Add skip_nolint and skip_nolint_exclude attributes to nogo rule

In a large codebase (monorepo) with established technical debt, //nolint directives can accumulate and hide legitimate issues from static analysis. While nogo supports per-analyzer exclude_files configuration, there's no way to globally enforce analyzer checks while making targeted exceptions (e.g., for test files, mocks, or generated code).

This proposal adds two new attributes to the nogo rule:
- skip_nolint (bool): When true, ignores all //nolint directives, forcing analyzers to report all findings
- skip_nolint_exclude (string_list): Glob patterns for files where nolint directives should still be respected

This enables peeps to progressively reduce technical debt by:
1. Setting skip_nolint = True to prevent new violations from being suppressed
2. Using skip_nolint_exclude = ["*_test.go", "*/testdata/*", "*/mocks/*"] to maintain pragmatic exceptions
3. Gradually fixing production code violations without disrupting test code

Similar to how golangci-lint supports --enable-all with targeted exclusions, this provides a path for codebases to enforce stricter linting standards without requiring a big-bang migration.

Locate the nogo rule's attribute parsing and the code that handles //nolint directives, then trace how per-analyzer exclusions are applied. Confirm the new boolean and glob-list attributes are accepted and that nolint directives are ignored globally or respected only for matching files, with coverage in the relevant existing tests.

Written by the indexing model from the issue text.