Increase build number

[jan-janssen]

Checklist

• [ ] Used a personal fork of the feedstock to propose changes
• [ ] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jan-janssen]

@conda-forge-admin, please rerender

[jan-janssen]

Just to check if the windows builds fail here as well.

[jan-janssen]

C:\Program Files\Microsoft Visual Studio\2022\Enterprise>CALL "VC\Auxiliary\Build\vcvars64.bat" -vcvars_ver=14.29 10.0.22621.0 
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.6.4
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
        1 file(s) copied.
        1 file(s) copied.
        1 file(s) copied.
You need to run patch_libtool bash function after configure to fix the libtool script.
If your package uses OpenMP, add llvm-openmp to your host and run requirements.
make: *** No targets specified and no makefile found.  Stop.