Look in /etc/apt/sources.list.d/ and see if you have a file named like google-chome.list or similar.
In that file, there should be a line starting with deb. Make sure that line is not commented out. If it is, remove the # at the beginning and re-run the apt update/upgrade.
If you ran a do-release-upgrade or otherwise upgraded the major release of Ubuntu since you installed google chrome, that repo gets disabled during the upgrade and must be manually re-enabled afterwards. During the upgrade, a comment is added to the file indicating this. (And your comments indicate that this happened when you upgraded to noble.)
The file always contains a comment saying that modifications to the file may be lost. This means that when chrome gets updated, it may update the contents of that file. Even if the file does get updated, the enabled/disabled state of the deb line is preserved. The comment means exactly what it says.
Also, if you have a google-chrome.list.distUpgrade file, apt will ignore that file, as it is a backup of the other file named above. If you don't have a corresponding google-chrome.list file, rename the distUpgrade file back, and edit it to remove the # in front of deb. Otherwise, you can delete he backup file and edit the .list file instead.