Implement basic mod lints

[jieyouxu]

This PR adds a new cli action ActionLint, run as drg_mod_integration lint $PROFILE, to perform some basic mod lints for the given $PROFILE. This PR also adds a mod lint button and a lint report GUI.

Currently implemented mod lints:

• Lint mod conflicts.
• Lint AssetRegistry.bin.
• Lint incorrectly included shader files.
• Lint outdated pak version.
• Lint empty archive.
• Lint archive containing only non-pak files.
• Lint archive containing multiple paks.

Some basic manual testing can be done by creating a "test" profile which consists of two mods:

1. https://mod.io/g/drg/m/cave-leech-obi-wan-hello-there#1937463
2. https://mod.io/g/drg/m/spy-leech#2040409 (this has shader bytecode)

Pending Work

• Need to add some integration tests for the basic lints. We'd probably want to have some test mods for testing mod integration as well anyway.

cc #39.

[trumank]

It's not clear to me what test_mod_batches is supposed to me. I would opt for test_assets to contain anything test-related that's not actual code.

I'm also considering not including any archives (zip or pak) in the repo at all and instead build them from loose files when needed. This would make modification easier and would also provide more meaningful diffs. However, any tests are better than no tests so I'm find with how it is currently. Something to think about for future improvements.

[jieyouxu]

It's not clear to me what test_mod_batches is supposed to me. I would opt for test_assets to contain anything test-related that's not actual code.

Renamed to test_assets.

I'm also considering not including any archives (zip or pak) in the repo at all and instead build them from loose files when needed. This would make modification easier and would also provide more meaningful diffs.

I agree with this, though it would require the integration tests to have a build step and I'm not very sure how that would be nicely handled.