Prevent ESPHome from breaking when an update is released. Forced to update constantly

**Describe the problem you have/What new integration you would like**
Everytime the libraries get a bit out of date, building/flashing firmware breaks. Seems like the code is constantly checking what's available online instead of either requesting if I want to pull the latest or using what is already downloaded.

**Please describe your use case for this integration and alternatives you've tried:**
An example I have that is a constant sticking point for me. I run a lot of Kauf HA bulbs. I build and flash custom configuration on them as I add new bulbs/replace broken bulbs. I just had a bulb go out and I'm trying to flash an existing configuration onto the new bulb. WHen I go to build, i get an error that suddenly a field doesn't exist anymore. I was running ESPHome 2024.12 and had flashed several bulbs without issue. However even though the container is 5 months out of date, it tries to pull the latest config/build files and everything fails to build.

Normally I simply update esphome to the latest and then it works. However the base config file for the kauf bulbs has not been updated with esphome 2024.12. So now I had perfectly functioning configuration for bulbs that I am currently unable to just press build/flash on and instead am now chasing down whatever function was apparently deprecated.

I'm primarily JUST flashing bulb configurations, and I don't want to be constantly forced to be on the latest ESPHome version because updates often times break stuff.

**Additional context**
Also, I frequently have to ssh in and remove the .esphome/packages and external_components folders to get builds to work again when I update ESPHome. There should be a way to force a "clean" or a prompt when building firmware in the UI. Just chased my tail on this for 30 minutes.

Start by reproducing a build from an older ESPHome container using an existing bulb configuration, observing access to .esphome/packages and external_components and the UI build flow. Done would mean existing configurations are not forced to use newly released dependencies, with a documented way to clean cached packages or prompt before doing so.

Written by the indexing model from the issue text.