[depend-info] Turn errors into warnings when querying dependencies of unsupported triplet

[JackBoosY]

In PR #184, we terminate the command early according to the supports field in CONTROL/vcpkg.json, which affects the command depend-info, and it does not support the parameter --allow-unsupported.

Now these error messages are always treated as warnings.

[BillyONeal]

+1 -- I would go even farther and just make this the default. depend-info is not a system-mutating operation and does not take appreciable time so blocking the unsupported entries isn't really useful.

[Neumann-A]

appreciable time so blocking the unsupported entries isn't really useful.

unless you want to know why something in CI is skipped.

[BillyONeal]

appreciable time so blocking the unsupported entries isn't really useful.

unless you want to know why something in CI is skipped.

We should still be printing the warning, we just shouldn't block other depend-info data when the warning happens.

[JackBoosY]

@BillyONeal Sadly, if we always set it to Dependencies::UnsupportedPortAction::Warn and discard --allow-unsupported, these warnings will never be printed:

vcpkg-tool/src/vcpkg/dependencies.cpp

Line 894 in 8553f67

m_warnings.push_back("Warning: " + msg);

So I modifed this line to:

print2(Color::warning, msg + "\n");

But I don't know if it will affect the follow-up process.

[autoantwort]

vcpkg-tool/src/vcpkg/dependencies.cpp

Line 894 in 8553f67

m_warnings.push_back("Warning: " + msg);

So I modifed this line to:

print2(Color::warning, msg + "\n");

Don't do that. Do it like here and print the warnings that were returned by create_feature_install_plan

[JackBoosY]

@BillyONeal Can we merge this now?