Implications of LeaderLeaseTimeout being shorter than HeartbeatTimeout

LeaderLeaseTimeout is commented as
`LeaderLeaseTimeout is used to control how long the "lease" lasts for being the leader without being able to contact a quorum of nodes. If we reach this interval without contact, we will step down as leader.`
In default config, the HeartbeatTimeout is one second and LeaderLeaseTimeout is half second.
Does this configuration force the leader to step down even if heartbeats are being sent and received regularly on average, but just not frequently enough within the lease period?

Start by tracing the Go definitions and default configuration for LeaderLeaseTimeout and HeartbeatTimeout, then inspect the leader lease decision path. Confirm whether regular heartbeats can still miss the shorter lease window; done is a documented, maintainer-approved explanation of their interaction and any resulting configuration guidance.

Written by the indexing model from the issue text.