fix: scheduler init data dir

[mikeee]

Description

Creates the directory to mount by default

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #1416

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 11 lines in your changes missing coverage. Please review.

Project coverage is 21.83%. Comparing base (ddf43a5) to head (c0d30fa).
Report is 3 commits behind head on release-1.14.

Files	Patch %	Lines
pkg/standalone/standalone.go	0.00%	11 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           release-1.14    #1430      +/-   ##
================================================
- Coverage         21.94%   21.83%   -0.11%     
================================================
  Files                40       40              
  Lines              4913     4937      +24     
================================================
  Hits               1078     1078              
- Misses             3754     3778      +24     
  Partials             81       81              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[yaron2]

cc @JoshVanL

[mikeee]

Appears to work on mac but is having issues on Linux. Converting to draft

[JoshVanL]

It's very rare that a user would want to create local directory which is mounted into scheduler. There is very little the user can do with the data as it's raw ETCD & proto. Container runtime local volumes are the canonical approach, which are still accessible via the filesystem, but have no user permission issues- we are even doing a 777 here which we never want to be doing.

If a user did want to do this for whatever reason- they can per-create the local volume to a local relative path and use the --scheduler-volume to mount that.