fix(config): snapshot.module accept { timestamp: true}

[SoonIter]

Summary

close #6381

{ timestamp: true} should has the same meaning of { timestamp: true, hash: false }

We need to process this default value when we pass it to rust side.

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rspack canceled.

Name	Link
🔨 Latest commit	e3ba82e
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/662f1fb7174c6800072d6827

[SoonIter]

@ahabhgk
Is this change right?

// rspack.config.ts
snapshot: {
    module: {
      hash: true,
    },
    resolve: {
      hash: true,
    },
}

This config should expectedly correspond to

// rspack.config.ts
snapshot: {
    module: {
      hash: true,
      timestamp: false,
    },
    resolve: {
      hash: true,
      timestamp: false,
    },
}

but after this change

    D(snapshot, "module", {});
	assertNotNill(snapshot.module);
	D(snapshot.module, "timestamp", true);
	D(snapshot.module, "hash", production);

it will be correspond to 🤔

// rspack.config.ts
snapshot: {
    module: {
      hash: true
      timestamp: true,
    },
    resolve: {
      hash: true,
      timestamp: true,
    },
}

{ hash: true } { timestamp: true } and { timestamp: true, hash: true } should be three different behaviors.
I think this is a very misleading configuration.

https://webpack.js.org/configuration/other-options/#builddependencies

{ hash: true } -> { timestamp: false, hash: true }
{ timestamp: true } -> { timestamp: true, hash: false }
{ timestamp: true, hash: true }

[ahabhgk]

Oh I see.. Would you send another PR?

[SoonIter]

Would you send another PR?

My pleasure, #6399