vstart.sh: simplify crimson core assignment, use assign_crimson_cores.py

vstart.sh: simplify crimson core assignment, use assign_crimson_cores.py

This commit simplifies the internal flow in a few ways:
- core assignment is entirely handled by prep_balance_cpu and
  do_balance_cpu.  The latter simply does as the cpu_table
  instructs.
- assign_crimson_cores calls lscpu and taskset internally, no
  need for temp files.

It also changes some defaults:
- if crimson-balance-cpu is unset or set to none, crimson-osd will not
  pin cpus at all rather than using the simple sequential allocation
  scheme, which could be much less efficient on platforms where
  cpuids 0,1,2,3,... are on socket 0,1,2,3,...  "osd" and "socket"
  options provide numa aware assignments when requested.

New features:
- Alienstore cores are now assigned with assign_crimson_cores
  using the same balance strategy using
  --crimson-alien-num-cores.
- --crimson-reactor-physical-only and
  --crimson-alienstore-physical-only will cause reactor or
  alienstore cpus respectively to be allocated with one
  cpu per physical core rather than including smt siblings.

Fixes: https://tracker.ceph.com/issues/71096
Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit 1795f46ebbc2f061e26f0298815d891fa12c1b96)