Update ncurses to latest.

[vaikas]

While working on the package tests for melange, noticed the ncurses was failing:
https://github.com/chainguard-dev/melange/actions/runs/7008726917/job/19065682639?pr=864

⚠️  x86_64    | --2023-11-27 17:40:51--  https://invisible-mirror.net/archives/ncurses/current/ncurses-6.4-20230722.tgz
⚠️  x86_64    | Resolving invisible-mirror.net... 160.153.42.69
⚠️  x86_64    | Connecting to invisible-mirror.net|160.153.42.69|:443... connected.
⚠️  x86_64    | HTTP request sent, awaiting response... 404 Not Found

And sure enough, it's not there anymore. So bump the later one.

Fixes:

Related:

Pre-review Checklist

For new package PRs only

• This PR is marked as fixing a pre-existing package request bug
  • Alternatively, the PR is marked as related to a pre-existing package request bug, such as a dependency
• REQUIRED - The package is available under an OSI-approved or FSF-approved license
• REQUIRED - The version of the package is still receiving security updates
• This PR links to the upstream project's support policy (e.g. endoflife.date)

For new version streams

• The upstream project actually supports multiple concurrent versions.
• Any subpackages include the version string in their package name (e.g. name: ${{package.name}}-compat)
• The package (and subpackages) provides: logical unversioned forms of the package (e.g. nodejs, nodejs-lts)

For security-related PRs

• The security fix is recorded in the advisories repo

For version bump PRs

• The epoch field is reset to 0

For PRs that add patches

• Patch source is documented

[vaikas]

Bleh, I just noticed #9086 that seems to tackle this.

[hectorj2f]

Don't you need to update the epoch?

[vaikas]

Don't you need to update the epoch?

doh, I need to drop it back to 0 since version increased.