Use reusable workflow for build and tests

[masesdevelopers]

Description

Extract the bulk of build and test jobs into a new reusable workflow (.github/workflows/build_functions.yaml) and update .github/workflows/build.yaml to call it. The top-level workflow name was changed to "Build and test" and a weekly schedule (cron) was added. The new call forwards inputs and secrets (ExecuteOnMoreOSes, ForceContinueOnError, EnableProcessDump, ProcessDumpType, EnableVerboseDiagnosticProcessDump, actor, GITHUB_TOKEN, JCOBRIDGE_ENCODED) and grants pull-requests write permission. This refactors and modularizes CI logic to reduce duplication and make the build/test pipeline reusable.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.