Use Stratum device config binary format

[Yi-Tseng]

This pull request change the pipeline config format for all profiles and platforms

Parts modified:

• build.sh script: use pipeline builder container to create the pipeline config instead of the tarball.
• PTF tests: use the new pipeline, and set the device to stratum-bfrt for all cases since both target can use that format.
• Pipeconf: both stratum_bf and stratum_bfrt uses the new pipeline config format.

TODO:

• Should we merge stratum_bf and stratum_bfrt pipeconf? Both targets can now use the same pipeline config format
• Should we use the latest version/tag of the stratum-bf-pipeline-builder container image? (not harmful to just use the latest version with shasum for now)

Closes #39

[pudelkoM]

Considering the bfrt branch is still under active development, pinning the pipeline builder by checksum is probably not a bad idea. We can switch to a release-tagged version once we have a Stratum release with the builder in it.

[codecov]

Codecov Report

Merging #118 into master will increase coverage by 1.10%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #118      +/-   ##
============================================
+ Coverage     68.59%   69.70%   +1.10%     
  Complexity      224      224              
============================================
  Files            17       17              
  Lines          1640     1614      -26     
  Branches        135      133       -2     
============================================
  Hits           1125     1125              
+ Misses          440      414      -26     
  Partials         75       75              

Impacted Files	Coverage Δ	Complexity Δ
.../org/stratumproject/fabric/tna/PipeconfLoader.java	0.00% <0.00%> (ø)	0.00 <0.00> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 155c142...bd145fc. Read the comment docs.