Problem:

In MTR, we have different include files which is sourced within the MTR tests to
check for certain dependencies on which the test will rely. If the dependencies
are not satisfied, the tests are skipped.
This can be risky because we may end up with tests that are never run because
the conditions are never met in PB2.

Fix:

1. A new MTR option (--no-skip) is introduced. This option will allow each
MTR test to run without any skip. This will ensure all the tests are run.

2. An excluded list is maintained to keep track of tests which should
continue to skip to avoid unwanted failures.

3. The default value of this introduced variable will be OFF. This implies that
users will not be forced to run all the tests and they will not have to deal with
unwanted failures due to missing dependencies.

Reviewed by:
Anitha Gopi <anitha.gopi@oracle.com>
Sayantan Dutta <sayantan.dutta@oracle.com>
RB: 12004