Separate top level dataflow concept from layer strategy

Created by: jmitrevs

While updating the configuration, I think we should separate out the concept of top-level dataflow vs pipeline from the layer strategy. Currently, the _validate_conv_strategy could inadvertently change a Dense layer in the model from Latency to Resource. I think the concepts are different enough that they should have different configuration parameters.