fix: update-rules version check

[fukusuket]

What Changed

• Closed [bug] Wrong message in update-rules command in ver 3.0.0-dev #1524
  • This issue only occurs in the dev version.

Evidence

% ./hayabusa

┏┓ ┏┳━━━┳┓  ┏┳━━━┳━━┓┏┓ ┏┳━━━┳━━━┓
┃┃ ┃┃┏━┓┃┗┓┏┛┃┏━┓┃┏┓┃┃┃ ┃┃┏━┓┃┏━┓┃
┃┗━┛┃┃ ┃┣┓┗┛┏┫┃ ┃┃┗┛┗┫┃ ┃┃┗━━┫┃ ┃┃
┃┏━┓┃┗━┛┃┗┓┏┛┃┗━┛┃┏━┓┃┃ ┃┣━━┓┃┗━┛┃
┃┃ ┃┃┏━┓┃ ┃┃ ┃┏━┓┃┗━┛┃┗━┛┃┗━┛┃┏━┓┃
┗┛ ┗┻┛ ┗┛ ┗┛ ┗┛ ┗┻━━━┻━━━┻━━━┻┛ ┗┛
   by Yamato Security

Hayabusa v3.0.0 - Dev Build
Yamato Security (https://github.com/Yamato-Security/hayabusa - @SecurityYamato)

Usage:
  hayabusa.exe <COMMAND> [OPTIONS]
  hayabusa.exe help <COMMAND> or hayabusa.exe <COMMAND> -h

Commands:
  computer-metrics     Output the total number of events according to computer names
  csv-timeline         Create a DFIR timeline and save it in CSV format
  eid-metrics          Output event ID metrics (total number and percent of events, channel, ID, event name)
  extract-base64       Extract and decode base64 strings from events
  json-timeline        Create a DFIR timeline and save it in JSON/JSONL format
  level-tuning         Tune alert levels for the DFIR timeline (default: ./rules/config/level_tuning.txt)
  list-contributors    Print the list of contributors
  list-profiles        List the output profiles for the DFIR timeline
  log-metrics          Output evtx file metadata (filename, computer names, number of events, first and last timestamps, channels, providers)
  logon-summary        Output a summary of successful and failed logons
  pivot-keywords-list  Create a list of pivot keywords
  search               Search all events by keyword(s) or regular expression
  set-default-profile  Set default output profile for the DFIR timeline
  update-rules         Update to the latest rules in the hayabusa-rules github repository
  help                 Print this message or the help of the given subcommand(s)

fukusuke@MacBookAir hayabusa-2.19.0-mac-aarch64 % ./hayabusa update-rules -q
Start time: 2024/12/04 23:14

You currently have the latest rules.

I would appreciate it if you could check it out when you have time🙏

[YamatoSecurity]

@fukusuket Thanks for noticing this and fixing it! LGTM!