Cannot run a packaged project if the project uses a Built-In Editor plugin and the project was packaged with the Build setting set to "Never"

This may be related to [Link Removed].

A packaged project will fail to run successfully if the project includes a Built-In Editor plugin and the project was packaged with the Build option set to "Never".

1. Create a new Basic Code project.
2. Open the project in the Editor.
3. Open the project's Packaging Settings and make sure the Build option is set to "If project has code, or running a locally built editor".
4. Package the project for Development Win64.
5. Run the packaged project.
6. When the packaged project opens a black screen, open the console and enter "quit" to exit.
7. Optional: Delete the packaged project.
8. Open the Plugins window.
9. Enable any Built-In Editor plugin that is not already enabled (tested with the Actor Sequence Editor and glTF Importer plugins, as well as with a new custom plugin added to the Engine).
10. Restart the Editor.
11. Open the project's Packaging Settings.
12. Set the Build option to "Never".
13. Package the project for Development Win64.
14. Run the packaged project.

RESULT:
The packaged project does not run successfully. Looking at the log file for the project, an error similar to the following is seen: LogPluginManager: Error: Unable to load plugin 'ActorSequenceEditor'. Aborting.

EXPECTED:
The packaged project runs successfully.

WORKAROUND:
Disable the plugin prior to packaging, or package once with the Build option set to "If project has code, or running a locally built editor".