Use parameters and keyword args for opts at top level

- Instead of passing a benchmark-opts?, each parameter
  can be specified for each of mk-bench... type functions
- Add parameters for each of the options formerly in benchmark-opts?
- Also add a #:opts keywork for internal use (passin benchmark-opts?)
Examples now use keywords args and parameters
--deps auto, not force for link_install target
Only associate options with benchmark-one?

- Parameterize can be used to introduce other scopes
- keyword arguments or parameterize can be used for affecting
  benchmark options for a benchmark-one?
- only mk-bench-one supports keyword arguments right now
Make examples use new scheme of applying benchmark opts