fix-bug: can not register again when heartbeat response 404

[darcydai]

The main changes in the current PR are as follows:

1. When the Eureka server crashes or encounters a network issue, the registration information on the Eureka server side will expire. When the client sends a heartbeat again, the server will return an HTTP 404 status code. Upon receiving this status code, the client will trigger a re-registration. This logic is present in the Java version.
2. During the service startup, the Java client does not actually register with the status STARTING and then update to UP. Based on my debug verification of the Java version, it registers directly with the status UP. Therefore, registering and then modifying the status is meaningless.