chainlink Start `inBackupHealthReport` during migrations

Rename the InBackupHealthReport to StartUpHealthReport
Start the StartUpHealthReport in the handleNodeVersioning method so it would cover both db migrations and backups
Stop using the DefaultServeMux to avoid issues when testing migrations and rollbacks

May 07 '24 14:05 george-dorin

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

#added For any new functionality added.
#breaking_change For any functionality that requires manual action for the node to boot.
#bugfix For bug fixes.
#changed For any change to the existing functionality.
#db_update For any feature that introduces updates to database schema.
#deprecation_notice For any upcoming deprecation functionality.
#internal For changesets that need to be excluded from the final changelog.
#nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
#removed For any functionality/config that is removed.
#updated For any functionality that is updated.
#wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.