[bug] conan lock bundle: existing packages are returned in build-order

[GordonJess]

Environment Details (include every applicable attribute)

• Operating System+version: Windows 10 (64-bit)
• Compiler+version: n/a
• Conan version: 1.34.0
• Python version: 3.7.3

Steps to reproduce (Include if Applicable)

# config
conan config set general.default_package_id_mode=package_revision_mode
conan config set general.revisions_enabled=True

# create lockfiles
conan lock create --reference=app1/0.1@user/channel --profile=windows_ctc_debug --lockfile-out=app1_0.1_user_channel_windows_ctc_debug.lock --build=missing 
conan lock create --reference=app1/0.1@user/channel --profile=windows_ctc_release --lockfile-out=app1_0.1_user_channel_windows_ctc_release.lock --build=missing 
conan lock create --reference=app2/0.1@user/channel --profile=windows_ctc_debug --lockfile-out=app2_0.1_user_channel_windows_ctc_debug.lock --build=missing 

# create bundle
conan lock bundle create --bundle-out=bundle.lock app1_0.1_user_channel_windows_ctc_debug.lock app1_0.1_user_channel_windows_ctc_release.lock app2_0.1_user_channel_windows_ctc_debug.lock

# calculate build order
conan lock bundle build-order bundle.lock

Logs (Executed commands with output) (Include/Attach if Applicable)

For some reason cmake_installer is returned in the build order, even though this package (package_id and prev) already exists in the cache.

> conan lock bundle build-order bundle.lock
[['cmake_installer/3.15.3@conan/stable#0'], ['liba/0.1@user/channel#7cb1b515df9f2edca15c6be7b407fd9f3360687c'], ['libb/0.2@user/channel#e2bd59050424c9f52887b3a57f51fbbe4c0183c2', 'libc/0.1@user/channel#0a625f367ed65a23f19c651ab15def372f515885'], ['app2/0.1@user/channel#075699c801b905b6a59945c44175284d31914a3c', 'libd/0.1@user/channel#5330c969604da6c0be25f776c617cc5e0ee88b6f'], ['app1/0.1@user/channel#b700b18e79f23bfff464602037684bdbc62ac4d2']]

bundle.zip

[solvingj]

Confirmed bug. Will be worked on today most likely.

[memsharded]

Fix submitted in #8579 for 1.34.1, thanks for detailed report!

[memsharded]

Fixed in #8579