Remove check for public and private scores to have same keys when using custom metrics

[ktrapeznikov]

We are setting up a competition where public and private metrics will have different names. For example, we may have different sub-splits or categories of the data reported on the leaderboards. The number and the name of these metrics will be different for public and private.

I see this constraint is checked here:

competitions/competitions/compute_metrics.py

Line 71 in 447fff1

if evaluation["public_score"].keys() != evaluation["private_score"].keys():

[github-actions]

This issue is stale because it has been open for 15 days with no activity.