Update lints table to contain Anchor and Non-Anchor columns

[S3v3ru5]

Updates readme to inform users which lints work on Anchor programs and which on Non Anchor programs.

[smoelius]

I'm not sure how I feel about this, TBH.

These points summarize my hesitation:

1. Package metadata is usually consumed by tools (e.g., cargo-udeps). So this use is somewhat unconventional.
2. Grepping the package metadata out of the Cargo.toml is kind of ugly. (On the flip side, any other approach would likely be more complicated.)
3. Users have to manually update this data. It would be nice if Anchor/non-Anchor support could be detected automatically.

But we can let it ride and see how it goes.

[S3v3ru5]

Thanks Sam. I agree with all your points. Are there other ways we can encode this information for a lint? I can try other approaches.