fix: editorconfig-linters dependency declaration scope

[kamil-perczynski]

Closes #10, but requires some discussion imho.

Although I understand the intent behind direct dependency only on the editorconfig-lint-api and narrowing the scope of the editorconfig-linters, hard-coded adding mavenCentral() causes issues in environments where manual repositories resolution is required: custom repositories resolution.

Specifically, I think about environments where access to software repositories is restricted/proxied due to security reasons (described in #10, I have recent professional experience with such setup - becoming an industry standard I suppose).

Declaring linters package as implementation dependency looks like reasonable step:

• Sync with dependencies declaration with ec4j-maven-plugin
• Repositories configuration is 100% on the user side

[ppalaga]

Thanks @kamil-perczynski, what you say sounds reasonable.