Had similar issues around msdyn_salessuggestion as a dependency when moving from dev to a new environment.
the old environments which we stood up in Sept and Nov 2021 included msdyn_salessuggestion as a entity. The connected solution "msdynce_SalesInsightsAnchor" seems to be a under the hood solution (doesnt show in solutions list).
New environments created late Feb / early March 2022 does not contain this entity (you can see this in advanced find "suggestion" so any import of solutions with the full account (and afew other entries) will fail....
<MissingDependency>
<Required type="1" schemaName="msdyn_salessuggestion" displayName="Suggestion" solution="msdyn_acceleratedsales (9.1.2201.5004)" typeName="Entity">
<package>msdynce_SalesInsightsAnchor (9.0.22013.10009)</package>
</Required>
<Dependent type="1" schemaName="account" displayName="Account" typeName="Entity" />
</MissingDependency>
<MissingDependency>
Spent a lot of time on this (trying to find out how it was installed, why its different, remove it from dev or install it in new environments / configure sales hub etc), but end of it, MS seems to have applied some push a few days ago which has addressed the issue, the new environments seem to now have this dependency so imports are now working..... You can check the solution history records and see this, and also doing advanced finds, you should now see "suggestion"... glad they fixed it but very disappointed on their black magic changes in the background (which i suspect likely created this situation, as well as it having fixed it...)
prob needs better quality control rather then use us as genie pigs (costed a week of digging and rebuilding environments etc and kind of says to me they don't really care about our time wasted / implications of their changes)
MS magic fix?
No suggestion entity before hand
now like magic....