docs: Rework extra blueprints to separate DB tools image and kanister-tools image

[hairyhum]

Change Overview

Follow up to #3284

Pull request type

Please check the type of change your PR introduces:

• [ ] :construction: Work in Progress
• [ ] :rainbow: Refactoring (no functional changes, no api changes)
• [ ] :hamster: Trivial/Minor
• [ ] :bug: Bugfix
• [ ] :sunflower: Feature
• [x] :world_map: Documentation
• [ ] :robot: Test
• [ ] :building_construction: Build

Issues

• fixes #issue-number

Test Plan

• [ ] :muscle: Manual
• [ ] :zap: Unit test
• [ ] :green_heart: E2E

[hairyhum]

Blocked by https://github.com/kanisterio/kanister/pull/3330

No longer blocked.

[viveksinghggits]

@hairyhum , should we update ALL the blueprints? Or should we just add a new example with the blueprint that uses the newly introduced kanister functions. I am suggesting this because if this change doesn't significantly change the way users create/work on blueprints, and we change blueprints in the examples, users might get confused if they look into the new blueprints. what do you think?

[Shrekster]

Already merged, but LGTM. Thanks!