[PLA-2033] Add AuctionData back

[leonardocustodio]

PR Type

enhancement

---

Description

• Added a new AuctionData type to the ListingStorage.json file, which includes startBlock and endBlock fields.
• Enhanced the ListingData enum to incorporate the newly added AuctionData type.

---

Changes walkthrough 📝

	Relevant files
Enhancement	ListingStorage.json Add `AuctionData` type and enhance `ListingData` enum        src/Services/Processor/Substrate/Codec/Types/ListingStorage.json Added AuctionData type with startBlock and endBlock fields. Enhanced the ListingData enum to include AuctionData. +4/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Ensure consistency in data types used for block numbers across the system Ensure that the "Compact" type used for "startBlock" and "endBlock" in "AuctionData" is consistent with the rest of the system's handling of block numbers. If the system uses a different type for block numbers elsewhere, consider aligning them to prevent type mismatches. src/Services/Processor/Substrate/Codec/Types/ListingStorage.json [28-30] "AuctionData": { - "startBlock": "Compact<u32>", - "endBlock": "Compact<u32>" + "startBlock": "AlignedType", + "endBlock": "AlignedType" } Suggestion importance[1-10]: 7 Why: The suggestion highlights a potential inconsistency in data types for block numbers, which could lead to type mismatches. Ensuring consistency across the system is important for maintainability and correctness, but the suggestion is not directly actionable as it requires verification of existing system types.	7