Fix daemon startup latency issue by providing an option to skip snaps…

[Shubhranshu153]

…hotter supported flag

Issue #, if available:
Soci Daemon startup time was long when undergoing simultaneous intense io operations.

Description of changes:
Add a config option to skip snapshotter is supported check that an user can configure

Testing performed:

1. Test with no option provided in config.toml. This is the default case. There is no change in behaviour
2. Test with option true in config.toml

Jun 19 17:05:40 ip-172-31-24-167 soci-snapshotter-grpc[9163]: {"level":"info","msg":"starting soci-snapshotter-grpc","revision":"944f0361363540379f0872eb6d93f49e4365ec66.m","time":"2024-06-19T17:05:40.090552376Z","version":"944f036.m"}
Jun 19 17:05:40 ip-172-31-24-167 soci-snapshotter-grpc[9163]: {"level":"warning","msg":"Skipped snapshotter is supported check ","revision":"944f0361363540379f0872eb6d93f49e4365ec66.m","time":"2024-06-19T17:05:40.090751222Z","version":"944f036.m"}
Jun 19 17:05:40 ip-172-31-24-167 soci-snapshotter-grpc[9163]: {"emitMetricPeriod":10000000000,"fetchPeriod":500000000,"level":"info","maxQueueSize":100,"msg":"constructing background fetcher","silencePeriod":30000000000,"time":"2024-06-19T17:05:40.091041601Z"}
Jun 19 17:05:40 ip-172-31-24-167 soci-snapshotter-grpc[9163]: {"address":"/run/soci-snapshotter-grpc/soci-snapshotter-grpc.sock","level":"info","msg":"soci-snapshotter-grpc successfully started","time":"2024-06-19T17:05:40.091712667Z"}
Jun 19 17:05:40 ip-172-31-24-167 systemd[1]: Started soci-snapshotter.service - soci snapshotter containerd plugin.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[sondavidb]

Can we also update config/config.toml with this new config variable?

We may also want to add an integration test with this config option.