refactor(pr-review-club): follow existing schema

Use the `number` field instead of `issue` to refer to the
number of the related pull request. This follows the same
schema used for github metadata

scraper/models/documents.py

@@ -70,9 +70,9 @@ class BitcoinTranscriptDocument(ScrapedDocument):
 
 
 class PRReviewClubDocument(ScrapedDocument):
-    issue: Optional[int] = Field(
+    number: Optional[int] = Field(
         default_factory=None,
-        description="Bitcoin Core issue number associated with the meeting",
+        description="Bitcoin Core PR number associated with the meeting",
     )
     host: Optional[str] = Field(
         default=None, description="The person hosting the meeting"

scraper/scrapers/pr_review_club.py

@@ -52,12 +52,12 @@ def customize_document(
         For Bitcoin Core PRs, uses PR number and metadata.
         For other content, identifies topics from filename.
         """
-        document_data["issue"] = metadata.get("pr", None)
+        document_data["number"] = metadata.get("pr", None)
         document_data["host"] = metadata.get("host", [])
         document_data["tags"] = metadata.get("components", []) or []
 
         # If no PR number exists, this is not a Bitcoin Core PR review
-        if not document_data["issue"]:
+        if not document_data["number"]:
             # Extract title from filename
             title = self._extract_title_from_jekyll_filename(file_path)