Add IDSA scraper

[KouateMuhamed]

Summary

• Add an AMFV-native scraper for IDSA practice guidelines through the shared scraper registry.
• Include current and archived guidelines by default, exclude in-development records, and mark archived documents with quality_flags=["outdated"].
• Add quality metadata for short guideline pages and retrievable external/PDF links.
• Remove Table of Contents navigation and empty headings from scraped content.

Tests

• uv run ruff check datasets
• uv run ruff format --check datasets
• uv run pytest datasets/test

QA

• Scraped 79 current and archived IDSA documents from the live site with zero errors.
• Confirmed 25 archived documents carry the outdated quality flag.
• Confirmed metadata contains only HTTP/HTTPS links, every IDSA document has section_count=1, and generated Markdown has no empty headings.
• Retained short documents with quality_flags=["short_content"].

[CLAassistant]

All committers have signed the CLA.

[warner-benjamin]

Thanks for the PR. This looks good, but it also grabs out of date guidelines. If we process those we'll want to add a metadata flag that they are out of date.

[KouateMuhamed]

@zndr27 I addressed the review feedback in b60e4d6: archived guidelines are included by default and marked outdated, in-development records are excluded, link metadata is HTTP/HTTPS-only, empty headings are removed, and IDSA section_count is consistently 1. The datasets suite and Ruff checks pass; a live crawl completed 79/79 documents with 25 outdated and no metadata/link/heading issues. A re-review would be appreciated.

[KouateMuhamed]

@warner-benjamin CI run 32984321093 ended with startup_failure before any job step ran, so this is not a test failure. I cannot rerun it without repository admin permission. Local verification is green: 48 datasets tests, Ruff check, Ruff format check, and the 79-document live crawl all passed. Could a maintainer rerun the workflow?

[zndr27]

Thank you. @warner-benjamin pinging you for final approval