What would you like to be added: As title

Why is this needed: All pruning schedule except AGPPruner only support level, L1, L2. While there are FPGM, APoZ, MeanActivation and Taylor, it would be much better if we can choose any pruner with any pruning schedule.

**Without this feature, how does current nni

For example, if there is a relationship transaction.session_id -> sessions.id and we are calculating a feature transactions: sessions.SUM(transactions.value) any rows for which there is no corresponding session should be given the default value of 0 instead of NaN.

Of course this should not normally occur, but when it does it seems more reasonable to use the default_value.

`DirectF

Problem
Since Java 8 was introduced there is no need to use Joda as it has been replaced the native Date-Time API.

Solution
Ideally greping and replacing the text should work (mostly)

Additional context
Need to check if de/serializing will still work.

In the following file:
https://github.com/feast-dev/feast/blob/master/infra/charts/feast/values-batch-serving.yaml

stores:
      - name: historical
        type: BIGQUERY
        config:
          project_id: <google_project_id>
          dataset_id: <bigquery_dataset_id>

If you provide the actual dataset_id, which is in the format of project:dataset_name feast will not able

The AutoML crashes if all models have error. It should be handled more gently.

The example of crash:

AutoML directory: AutoML_88
The task is multiclass_classification with evaluation metric logloss
AutoML will use algorithms: ['MLP']
AutoML steps: ['simple_algorithms', 'default_algorithms', 'not_so_random', 'hill_climbing_1', 'hill_climbing_2']
Skip simple_algorithms because no parame