Restore process merge cookbook version diring fix of failed restore

Version:

v3.0.1
[Version of the project installed]

Environment:

Prod/Dev
[Details about the environment such as the Operating System, cookbook details, etc...]
Oracle Linux 7.9

Scenario:

During Backup restore process according to instruction if exist metadata.rb file and metadata.json, where metadata.rb version is lower than metadata.json, restore process somehow use metadata.rb version content instead of metadata.json. Chef server shows that latest version is same which in metadata.json, but clients downloading old version to cache.
After regular knife cookbook upload cookbook $name, everything fixed.
[What you are trying to achieve and you can't?]

Steps to Reproduce:

1. Create cookbook which have 2 different version in metadata
2. Backup
3. Start restore but fail
4. Start process again, and ask to fix failed restore.
5. Check content on hosts

Expected Result:

Versions content must be used from metadata.json, as most preferred

Actual Result:

Version from metadata.rb used for clients

Start by reproducing the failed restore retry with conflicting versions in metadata.rb and metadata.json on Oracle Linux 7.9, then trace the restore path that determines the cookbook version. Done means restored clients use the metadata.json version, matching the Chef server's latest version without requiring a regular knife cookbook upload.