Hot reloading forces a complete reload of the whole add-in

Prerequisites

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• [ x] I am running the latest version of Node and the tools
• [ x] I checked the documentation and found no answer
• [ x] I checked to make sure that this issue has not already been filed

Expected behavior

When a code source file is changed while debugging in VSC, hot reloading should make the change but leave the app in the same place where it was, so the developer doesn't have to go through the all the steps in the UI to get back to where they were.

Current behavior

The change in the source file cause the entire app to reload and returns the app to its default starting state. There is also an error in the VSC debugging console: "Cannot apply update. Need to do a full reload."

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. Sideload an add-in in VSC
2. Run the add-in.
3. Make a change in a code source file.

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: Windows 10
• Node version: 16.13.2
• Office version: 2302 16127.20000
• Tool version: ?

Failure Logs

Please include any relevant log snippets, screenshots or code samples here.

Reproduce the issue in VS Code using the listed Windows, Node, and Office versions, then inspect the debugging console message after changing a source file. Trace the hot-reload tooling entry point responsible for applying the update. Done means an add-in source change is applied without a full reload and the app remains in its current state.