ci(docker): use new LizardByte release methodolgy

[ReenigneArcher]

Description

This PR moves the docker ci to use the new setup release and create release actions. This will enable more of a "rolling" release model.

This will require testing before merging. Candidates for testing are "discord-bot" or "reddit-bot" repos.

Screenshot

Issues Fixed or Closed

• build(deps): bump easimon/maximize-build-space from 8 to 10 #297
• build(deps): bump actions/cache from 3 to 4 #310
• build(deps): bump peter-evans/dockerhub-description from 3 to 4 #315

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

[LizardByte-bot]

It looks like this PR has been idle for 90 days. If it's still something you're working on or would like to pursue, please leave a comment or update your branch. Otherwise, we'll be closing this PR in 10 days to reduce our backlog. Thanks!