feat: add sample file processing as post-deployment step 4

[Dongbumlee]

This pull request adds automated and documented support for uploading and processing sample claim file bundles as part of the post-deployment workflow for the Content Processing Solution Accelerator. Now, after schema registration, two sample claim bundles are processed automatically, enabling immediate end-to-end verification of the deployment. The documentation and post-deployment scripts have been updated to reflect and support this new workflow.

Key changes:

Post-deployment automation:

• Added logic to both post_deployment.ps1 and post_deployment.sh scripts to automatically upload and process sample claim bundles (claim_date_of_loss and claim_hail) after schema registration, including batch creation, file upload, and submission for processing. [1] [2]
• Introduced new bundle_info.json manifests in each sample bundle directory to map files to their schema classes, enabling automated and accurate file processing. [1] [2]

Documentation updates:

• Updated DeploymentGuide.md and AVMPostDeploymentGuide.md to document the new sample processing step, clarify that it is performed automatically when using azd up, and provide instructions for manual execution in AVM scenarios. [1] [2] [3] [4] [5]

Script output improvements:

• Standardized and clarified script output messages in post_deployment.ps1 for easier readability and consistency. [1] [2] [3]

These changes streamline the post-deployment experience, making it easier to verify that the solution is working as intended immediately after deployment.- Add bundle_info.json manifests for claim_date_of_loss and claim_hail

• Add Step 4 to post_deployment.ps1 and post_deployment.sh
  • Creates claim batch with schemaset ID
  • Uploads files with mapped schema IDs
  • Submits batch for workflow processing
• Update DeploymentGuide.md with new step and sample output
• Update AVMPostDeploymentGuide.md with manual sample processing instructions
• Normalize output prefixes: ASCII dashes for ps1, emojis for sh

Purpose

• ...

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information