Drop nfs_server and consoleport defaults

[ekohl]

Beaker defaults to consoleport 443, so specifying this is redundant and extremely noisy.

As for nfs_server, I could not find any code that uses it. It shows up in many markdown files and configs, but I've yet to find actual Ruby code that uses it.

[codecov]

Codecov Report

Base: 0.50% // Head: 0.50% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (629109c) compared to base (f990ac3).
Patch coverage: 0.00% of modified lines in pull request are covered.

❗ Current head 629109c differs from pull request most recent head 276c0e1. Consider uploading reports for the commit 276c0e1 to get more accurate results

Additional details and impacted files

@@          Coverage Diff           @@
##           master    #271   +/-   ##
======================================
  Coverage    0.50%   0.50%           
======================================
  Files          15      15           
  Lines        2565    2562    -3     
======================================
  Hits           13      13           
+ Misses       2552    2549    -3     

Impacted Files	Coverage Δ
lib/beaker-hostgenerator/data.rb	0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[bastelfreak]

mhm maybe that's only used internally at Puppet?

[ekohl]

Possible, but I think the should fix the tool to have a default then instead of requiring it to be specified everywhere.

[smortex]

The beginning looks okay, but my browser crash when I try to scroll down :-D Adding .diff at the end of the URI helps.

This look reasonable to me.

[ekohl]

I should have mentioned that it was mostly:

find test/fixtures -type f -exec sed -i '/consoleport: 443/d' {} +
find test/fixtures -type f -exec sed -i '/nfs_server: none/d' {} +

Then I fixed up 3 fixtures where CONFIG became nil instead of {}.