[Change] tests: bump version-tracking assertions 2.0.1 -> 2.0.2

Three version-tracking BATS assertions hardcoded the prior release
string and failed after the 2.0.2 cut:

  - tests/17-version.bats: VERSION file content and `maldet --help`
    output partial-match on the banner version
  - tests/01-install-cli.bats: `maldet -v` / `--version` partial-match

Fixture data carrying historical `2.0.1` markers (tests/40-session-index.bats
session.index records, tests/30-session-tsv.bats scanner_ver field,
tests/22-updates.bats update-channel fixtures) intentionally preserved —
those assert correct parsing/handling of historical version metadata,
not the running version of LMD.

Verified: deb12 + rocky9 both 1080/1080 on freedom-local Docker (anvil
unreachable at run time).

Author: rfxn

tests/01-install-cli.bats

@@ -252,8 +252,8 @@ setup_file() {
 @test "maldet -v and --version both show version" {
     run maldet -v
     assert_success
-    assert_output --partial "2.0.1"
+    assert_output --partial "2.0.2"
     run maldet --version
     assert_success
-    assert_output --partial "2.0.1"
+    assert_output --partial "2.0.2"
 }

tests/17-version.bats

@@ -11,12 +11,12 @@ setup_file() {
 
 @test "VERSION file contains current version" {
     run cat "$LMD_INSTALL/VERSION"
-    assert_output --partial "2.0.1"
+    assert_output --partial "2.0.2"
 }
 
 @test "maldet reports correct version" {
     run maldet --help
     assert_success
-    assert_output --partial "v2.0.1"
+    assert_output --partial "v2.0.2"
 }