Plugin: Use OnceCell instead of Lazy_statics

- Using OnceCell improved the performance and make it similar to
  resource as interface approach

Author: AmmarAbouZor

application/apps/indexer/wasm_plugin/client-inter/Cargo.lock

@@ -14,7 +14,6 @@ dlt-core = { path = "../../../../../../dlt-core" }
 serde = "1.0.201"
 chrono = "0.4.38"
 humantime = "2.1.0"
-lazy_static = "1.4.0"
 
 [lib]
 crate-type = ["cdylib"]

application/apps/indexer/wasm_plugin/client-inter/Cargo.toml

@@ -11,6 +11,7 @@ use dlt_core::{dlt, parse::dlt_message};
 
 use self::{formattable_msg::FormattableMessage, ft_scanner::FtScanner};
 
+#[derive(Debug)]
 pub struct DltParser {
     pub with_storage_header: bool,
     ft_scanner: Mutex<FtScanner>,

application/apps/indexer/wasm_plugin/client-inter/src/dlt_parser/mod.rs

@@ -1,9 +1,10 @@
 mod dlt_parser;
 
+use std::sync::OnceLock;
+
 use dlt_parser::DltParser;
 use exports::host::indexer::parse_client_inter::Guest;
 use host::indexer::parsing::{Error, ParseReturn};
-use lazy_static::lazy_static;
 use wit_bindgen::generate;
 
 generate!({
@@ -14,23 +15,24 @@ generate!({
     },
 });
 
-lazy_static! {
-    static ref PARSER: DltParser = DltParser::new();
-}
+static PARSER: OnceLock<DltParser> = OnceLock::new();
 
 struct Component;
 
 impl Guest for Component {
     fn init(configs: _rt::String) -> Result<(), Error> {
-        Ok(PARSER.init(configs))
+        let parser = DltParser::new();
+        parser.init(configs);
+        PARSER.set(parser).unwrap();
+        Ok(())
     }
 
     fn parse(data: _rt::Vec<u8>, timestamp: Option<u64>) -> _rt::Vec<Result<ParseReturn, Error>> {
-        PARSER.parse(data, timestamp)
+        PARSER.get().unwrap().parse(data, timestamp)
     }
 
     fn parse_res(data: _rt::Vec<u8>, timestamp: Option<u64>) {
-        PARSER.parse_res(data, timestamp)
+        PARSER.get().unwrap().parse_res(data, timestamp)
     }
 }
 

application/apps/indexer/wasm_plugin/client-inter/src/lib.rs

@@ -56,7 +56,7 @@ world parse {
 // Parse client using an interface without resources.
 // With this approach, the host doesn't need to instantiate the parser but the parser
 // doesn't have a reference to itself on the method and must save it's state using statics 
-// This approach is less performant than the ratio `1.04`
+// This approach's perfrmance is similar to the parser interface as resource approach
 interface parse-client-inter {
   use parsing.{error, parse-return};