refactor(ci): stable-daily tagging

[befanyt]

I have refactored the stable-daily tagging logic to make it much more readable. I hope M2 is happier with this code.
Reference: #1804

Psuedo logic:

if triggered by schedule and its not weekly_tag_day; then
    tag with stable-daily
else
    tag with stable stable-daily
fi

In the code, I used the explicit term stable instead of ${FEDORA_VERSION} to improve readability. I chose this because we are already in stable logic, so this would always be stable. If you prefer ${FEDORA_VERSION} I can, of course, put that back in.

Manual triggered run will produce: stable, stable-daily
Schedule triggered run on weekly_tag_day: stable, stable-daily
Schedule triggered run on non weekly_tag_days: stable-daily

On top of this I made changes that will allow you to manually build stable or stable-daily only by pushing a button.
Introduces the following workflows.

• Aurora Stable Daily - (builds aurora:stable-daily)
• Aurora Stable Weekly - (builds aurora:stable)
• Bluefin Stable Daily - (builds bluefin:stable-daily)
• Bluefin Stable Weekly - (builds bluefin:stable)

To make this possible I updated the above pseudo logic like so:

if triggered by schedule and its not weekly_tag_day; then
    tag with stable-daily
else if build_stable_weekly is false; then 
    tag with stable-daily
else if build_stable_daily is false; then 
    tag with stable
else
    tag with stable stable-daily
fi

build_stable_weekly and build_stable_daily are both set to true by default inn the reusable-build.yml and are toggled via the new workflow files.

[m2Giles]

This is fine for now, but it feels a bit like a belt and suspenders situation. We are being overly specific it feels like.

[m2Giles]

This is much more readable now.

That said I think we have room for improvements in the future.

[castrojo]

Builds are skewed, forcing this in. Thanks everyone!