Misleading doc comment for `use_network_action_output_cache`

[lf-]

FYI this comment suggests that the behaviour believed in in #246 is the case.

buck2/app/buck2_server/src/daemon/state.rs

Lines 151 to 159 in b41f897

	/// Whether to consult the offline-cache buck-out dir for network action
	/// outputs prior to running them. If no cached output exists, the action
	/// (download_file, cas_artifact) will execute normally.
	///
	/// This supports fully-offline builds, where network actions like
	/// download_file have an execution component that is inherently non-local (
	/// e.g. making a HEAD request against the remote artifact to determine if
	/// it needs to be downloaded again).
	pub use_network_action_output_cache: bool,

It sounds from #246 that this comment is straight up not the intended use case, so I'm very confused what the setting is for. I indeed want the same thing as them which is that http_archives with a given hash survive daemon restarts.