beacon: Change beacon renewal job interval

[jamescowens]

This PR changes the renewal job interval to 1 hour from 4 hours and adds additional logging.

The original interval, 4 hours, is not often enough given the additional restriction with respect to the scraper activation window (beacon consensus window). This has no effect on wallet resource use as the call is effectively a no-op unless a renewal can be actually performed.

[Copilot]

Pull Request Overview

This PR updates the beacon renewal job interval and enhances logging within the beacon renewal process. Key changes include:

• Adding logging to track the execution of the beacon renewal job.
• Logging a message when the beacon renewal is skipped due to being within the scraper beacon consensus window.
• Changing the renewal interval from 4 hours to 1 hour to increase the frequency of renewal operations.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/gridcoin/researcher.cpp	Adds log messages to better indicate when beacon renewal runs or skipped.
src/gridcoin/gridcoin.cpp	Updates the scheduling interval for the beacon renewal job.

Comments suppressed due to low confidence (2)

src/gridcoin/researcher.cpp:1143

• [nitpick] Consider updating the log format by adding a colon after 'INFO' for consistency with other log statements.

LogPrint(BCLog::LogFlags::BEACON, "INFO %s: Skipping beacon renewal while within scraper beacon consensus window.", __func__);

src/gridcoin/gridcoin.cpp:550

• Verify that reducing the beacon renewal interval from 4 hours to 1 hour will not negatively impact system performance under heavy load.

scheduler.scheduleEvery(Researcher::RunRenewBeaconJob, std::chrono::hours{1});