[Chapel Merge] Bump build version to 1 on 1.26 branch to reflect

Branch: refs/tags/1.26.0
Revision: d80a127
Author: tzinsky
Link: Bump build version to 1 on 1.26 branch to reflect late-breaking changes by bradcray · Pull Request #19577 · chapel-lang/chapel · GitHub
Log Message:

Merge pull request #19577 from bradcray/build-version-1-for-1-26

Bump build version to 1 on 1.26 branch to reflect late-breaking changes

[reviewed by @ronawho]

If I've kept my facts straight, this should bump the build version for the
1.26 branch to "1" the next time we respin the tarball, reflecting the
changes in Fix an MCM issue between AMs and PUTs in ofi msg-order-fence by ronawho · Pull Request #19575 · chapel-lang/chapel · GitHub.
Unfortunately, I won't feel confident that this is working as intended
until we merge and try to respin the tarball (either manually or via
Jenkins).

Elliot points out that with the current --version logic, this will only
show up with --devel --version (which looks like a mistake to me,
but one to fix back on main rather than here).

Modified Files:
M compiler/Makefile

Compare: https://github.com/chapel-lang/chapel/compare/1.26.0