fix(intel471_v2): Unentitled report type logs a recurring ERROR traceback

[mmolenda]

Description

With the verity471 backend and reports enabled, a report-type stream whose account lacks entitlement to that type logs a full ERROR stack trace every interval. It's not fatal — other report types keep working — but it's alarming and pollutes logs/alerting.

Environment

1. OS: All
2. Version: >= 7.260317.0

Reproducible steps

Steps to create the smallest reproducible scenario:

1. Run intel471_v2 with INTEL471_BACKEND=verity471 and reports enabled.
2. Use credentials not entitled to one report type (e.g. geopol_report).
3. Wait for that stream's interval and check the logs.

Expected output

A single concise warning that the account isn't entitled to that report type, then continue with the other report types — no ERROR traceback, no repeat.

Actual output

ERROR Job "Verity471GeopolReportsStream ..." raised an exception
... streams/core/base.py line 96, in get_bundles
verity471.exceptions.UnauthorizedException: (401)
HTTP response body: {"error":"Some(geopol_report) not in users access claims."}