fix(build): workaround for pyproject.toml build bug

[fubuloubu]

What I did

Noticed that if you are working with a more complex monorepo-style project where the bots are intended to build different than the rest of the project, that having a pyproject.toml present causes a big issues.

This PR allows side-stepping the issue by specifying either requirements.txt or requirements-bot.txt (the later takes precedence), while still letting ape install plugins found in pyproject.toml.

Additionally, I added a few more features to the docker build wrapper so it can produce tagged images natively, and added a push flag to silverback build. This actually should make it nicer to build for local use as well as for upcoming cluster registry direct push feature (that I still need to define)

Lastly, I more fully documented silverback build

How I did it

How to verify it

Try some commands

Checklist

• Passes all linting checks (pre-commit and CI jobs)
• New test cases have been added and are passing
• Documentation has been updated
• PR title follows Conventional Commit standard (will be automatically included in the changelog)

[fubuloubu]

p.s. I think that the build CI here will fail until it's released, due to how it's built

wonder if work on SilverbackLtd/build-action#5 could fix this...

[johnson2427]

I tried this locally, LGTM

I'll approve so you can move forward while I attempt to make a more complicated monorepo to stress this

[fubuloubu]

Temporarily restoring branch here, so CI can pass (until build-action is updated

[fubuloubu]

Okay, updated in SilverbackLtd/build-action#7