feat: added raster shared types and values for lower resolution feature support

[CL-SHLOMIKONCHA]

| Answer |
| ---------------- | -------------------------------------------------------------------------- |
| New feature | ✔ |

This pull request introduces new core schemas and types for polygon parts and tile deletion, refactors schema organization for better reuse, and updates the release process and configuration for alpha pre-releases. It also includes a minor bug fix and validation improvements. The most important changes are summarized below:

New Core Schemas and Types:

• Added polygonParts.schema.ts and tile.schema.ts to src/schemas/core/, introducing comprehensive Zod schemas for polygon parts (including intersection schemas) and tile deletion parameters, and exported them in the core index for wider use. [1] [2] [3] [4]
• Added corresponding core types for polygon parts and tiles in src/types/core/ and exported them in the index.

Schema Refactoring and Validation Improvements:

• Refactored ingestion polygon parts schema to import and reuse the new core partSchema instead of duplicating its definition, improving maintainability. Also updated jobType validation to use a Zod enum schema. [1] [2] [3] [4]
• Added a new validation for resolution threshold checks in the ingestion validation task schema.
• Tightened the productId validation pattern in ingestion constants to restrict the maximum length.

Constants and Type Consolidation:

• Moved SourceType definition from export constants to core constants for consistent usage across the codebase, and added MAX_ZOOM_LEVEL to core constants. [1] [2]

Release Process and Versioning:

• Updated the release workflow to better handle alpha pre-releases and standard releases, including logic for npm publish and configuration for release-please. [1] [2] [3] [4]
• Bumped the package version to 8.1.0-alpha.3 and updated the changelog accordingly. [1] [2] [3]

Bug Fixes:

• Simplified file extension handling in the tile deletion parameters base schema. [1] [2]

These changes collectively improve schema coverage, validation accuracy, code reuse, and release automation.| Question