Add Hetzner Object Storage bucket-cataloger module (#1876)

[ChrisJr404]

Summary

Closes #1876 ("Module TODO: Hetzner Buckets", filed by @TheTechromancer).

Hetzner offers S3-compatible Object Storage at three locations (Falkenstein fsn1, Nuremberg nbg1, Helsinki hel1), addressed at https://<bucket>.<location>.your-objectstorage.com/. cloudcheck already ships a Hetzner provider, so this PR just plugs a new bucket_hetzner module into the existing bucket_template.

Module

bbot/modules/bucket_hetzner.py — same shape as bucket_digitalocean.py:

• regions = ['fsn1', 'nbg1', 'hel1'] — all three Hetzner Object Storage locations documented here.
• base_domains = ['your-objectstorage.com']
• supports_open_check = True (S3-style ListBucketResult protocol).
• delimiters = ('', '-') — Hetzner bucket names allow dot/hyphen/underscore ([a-z0-9][a-z0-9-_\\.]{1,61}[a-z0-9] per cloudcheck regex), but only the no-delimiter and single-hyphen forms are useful for permutation enum.

Tests

test_module_bucket_hetzner.py is a focused smoke test:

• module loads without error
• cloudcheck_provider_name == 'Hetzner', base_domains, regions match expectations
• build_url('examplebucket', 'your-objectstorage.com', 'fsn1') returns 'https://examplebucket.fsn1.your-objectstorage.com/'
• the cloudcheck Hetzner provider is reachable from the module instance

$ pytest bbot/test/test_step_2/module_tests/test_module_bucket_hetzner.py
1 passed in 2.42s

Note for the maintainer

I started by extending `Bucket_Amazon_Base` like the other bucket tests, but the shared base depends on the cloudcheck provider regex separating bucket name and host into two groups. The current cloudcheck Hetzner regex matches `.your-objectstorage.com` without a region segment, so a fixture URL of `.fsn1.your-objectstorage.com` (which is what real Hetzner buckets look like) gets parsed with bucket-name = `.fsn1`, and the bucket-template's brute force then explodes the storage-bucket count past the asserts in the shared base test. Two ways to handle that down the road:

1. Extend the cloudcheck Hetzner regex to capture region as a separate group, then fold this test into the shared base, OR
2. Keep this minimal smoke-test shape and rely on the broader bucket_template tests for the cross-region brute-force coverage.

Happy to do (1) as a follow-up MR against blacklanternsecurity/cloudcheck if you'd prefer that path before this lands.

[TheTechromancer]

@ChrisJr404 Thanks for doing this!! I'll see about updating the regexes on the cloudcheck side, then circle back around.

[TheTechromancer]

Upstream cloudcheck PR:

• Better bucket regexes cloudcheck#259

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (ChrisJr404)[https://github.com/ChrisJr404]
❌ @TheTechromancer
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[codecov]

Codecov Report

❌ Patch coverage is 96.96970% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 91%. Comparing base (5be4993) to head (61b7a29).
⚠️ Report is 4 commits behind head on dev.

Files with missing lines	Patch %	Lines
bbot/modules/internal/cloudcheck.py	90%	1 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##             dev   #3073   +/-   ##
=====================================
- Coverage     91%     91%   -0%     
=====================================
  Files        437     439    +2     
  Lines      37509   37533   +24     
=====================================
+ Hits       33925   33943   +18     
- Misses      3584    3590    +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ChrisJr404]

I have read the CLA Document and I hereby sign the CLA