SAMZA-2420: Update CommandLine to use config loader for local config file

[kw2542]

This is backward incompatible and is only supposed to be included in Samza 1.5

Design:
https://cwiki.apache.org/confluence/display/SAMZA/SEP-23%3A+Simplify+Job+Runner

Changes:

1. Update CommandLine to use config loader instead of config factory
2. Removed common.properties and adds its values to each job config
3. Update CheckpointTool to read new offsets from local file only.

API Changes:

1. Add config-loader-factory and config-loader-properties in CommandLine to support specifying ConfigLoaderFactory and its properties needed to load config.
2. Remove config-factory and config-path in CommandLine to discountinue the usage of ConfigFactory
3. Update CheckpointTool to read new offsets from local file only, i.e. --new-offsets only supports local file URI now.

Upgrade Instructions:

All usages in CommandLine and its subclasses will switch from --config-factory & --config-path to --config-loader-factory & --config-loader-properties, including job launch.

Usage Instructions

For example,

--config-factory=org.apache.samza.config.factories.PropertiesConfigFactory --config-path=file:///location/file.txt

will be changed to

--config-loader-factory=org.apache.samza.config.loaders.PropertiesConfigLoaderFactory --config-loader-properties path=file:///location/file.txt

Tests

1. Unit tests
2. Test against Hello Samza example with

deploy/samza/bin/run-app.sh --config-loader-factory=org.apache.samza.config.loaders.PropertiesConfigLoaderFactory --config-loader-properties path=$PWD/deploy/samza/config/wikipedia-feed.properties

[mynameborat]

You will need to follow up this patch with another patch for samza-hello-samza.
Looks like website documentation also needs to be updated.

[cameronlee314]

Should this check for configLoaderFactoryOpt instead? Theoretically, the config loader factory won't need additional properties. You might also need to somehow validate or catch that not all config loader properties were specified for the config loader.

[kw2542]

configLoaderFactoryOpt has a default value of PropertiesConfigLoaderFactory.

This check is to be consistent with the previous check where we require a config path (URI) to pass to the legacy ConfigFactory, which in theory may not need URI either.

We may remove this check completely too, if we want to support the case where config loader factory does not need any properties at all.

[cameronlee314]

In the previous case (i.e. ConfigFactory), the configURI was a required argument for the interface, and I don't think you can have an empty URI. For ConfigLoaderFactory interface, it is required to pass a Config, but it is possible to have an empty Config, so I think you could just remove the check to handle the general case.
The additional complexity that the ConfigLoaderFactory brings is that each concrete type requires different configs to be in Config, so if there is an error due to a missing config value, then that's maybe where you need to do the parser.printHelpOn(System.err); System.exit(-1);.

[kw2542]

Make sense, removed the check.

The default concrete PropertiesConfigLoaderFactory is checking the properties itself too.