fix: ensure release tags are cronological

[ReenigneArcher]

Description

• Use hhmmss as build number instead of commit hash
• Remove padding from months and days

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[ReenigneArcher]

Alternative to this, use hhmmss as build number and remove commit7 hash entirely.

[codecov]

Codecov Report

Merging #18 (ffddfdd) into master (c3791c6) will increase coverage by 0.17%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   94.23%   94.40%   +0.17%     
==========================================
  Files           1        1              
  Lines         156      161       +5     
==========================================
+ Hits          147      152       +5     
  Misses          9        9              

Files	Coverage Δ
action/main.py	94.40% <100.00%> (+0.17%)	⬆️