pvf: use test-utils feature to export test only (#7538)

* pvf: use test-utils feature to export test only

* adding comment to test-utils feature

* make prepare-worker and execute-worker as optional dependencies and add comments to test-utils

* remove doc hidden from pvf testing

* add prepare worker and execute worker entrypoints to test-utils feature

* pvf: add sp_tracing as optional dependency of test-utils

* add test-utils for polkadot and malus

* add test-utils feature to prepare and execute workers script

* remove required features from prepare and executing

* Try to trigger CI again to fix broken jobs

---------

Co-authored-by: Marcin S <marcin@realemail.net>

polkadot/node/core/pvf/src/lib.rs

@@ -97,11 +97,11 @@ mod prepare;
 mod priority;
 mod worker_intf;
 
-#[doc(hidden)]
+#[cfg(feature = "test-utils")]
 pub mod testing;
 
 // Used by `decl_puppet_worker_main!`.
-#[doc(hidden)]
+#[cfg(feature = "test-utils")]
 pub use sp_tracing;
 
 pub use error::{InvalidCandidate, ValidationError};
@@ -118,7 +118,9 @@ pub use polkadot_node_core_pvf_common::{
 };
 
 // Re-export worker entrypoints.
+#[cfg(feature = "test-utils")]
 pub use polkadot_node_core_pvf_execute_worker::worker_entrypoint as execute_worker_entrypoint;
+#[cfg(feature = "test-utils")]
 pub use polkadot_node_core_pvf_prepare_worker::worker_entrypoint as prepare_worker_entrypoint;
 
 /// The log target for this crate.

polkadot/node/core/pvf/src/testing.rs

@@ -19,7 +19,6 @@
 //! N.B. This is not guarded with some feature flag. Overexposing items here may affect the final
 //!      artifact even for production builds.
 
-#[doc(hidden)]
 pub use crate::worker_intf::{spawn_with_program_path, SpawnErr};
 
 use polkadot_primitives::ExecutorParams;