workflows: make 3.0 releases latest

[patrick-stephens]

Updates CI to handle 3.0 releases as latest and move 2.2 series to non-latest.

Merge only when ready for 3.0 releases otherwise 2.2 releases will not be marked as latest in Github or container tags

---

Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

• Example configuration file for the change
• Debug log output from testing the change

• Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

• Run local packaging test showing all targets (including any new ones) build.
• Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

• Documentation required for this feature

Backporting

• Backport to latest stable release.

---

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

[patrick-stephens]

@edsiper this should only be merged once we're ready to start making 3.0 releases - otherwise it will stop 2.2 containers and releases being marked as "latest"