Fixing network payload rules parsing

[NachoEmbrace]

It seems that the remote config API was never updated with the suggested changes for network payload capture.
This resulted in network capture rules not being parsed correctly on this version of the SDK.

This PR contains the necessary changes for us to parse the old payload.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[github-actions]

	Warnings
⚠️	No CHANGELOG entry added.

Generated by 🚫 Danger Swift against 494222d

[ArielDemarco]

Considering the actual API wasn't updated... is there any value that were considering that could arrive to the SDK and we don't know how to handle? (the only one I remember is the status_code -1, but I think we handle that one)

[NachoEmbrace]

Considering the actual API wasn't updated... is there any value that were considering that could arrive to the SDK and we don't know how to handle? (the only one I remember is the status_code -1, but I think we handle that one)

The only big difference was the http method being a single string instead of an array and the expiration being the time until the rule expires instead of the expiration timestamp.
On top of that some keys have different names.

Other than that there are keys that could be present but will be ignored. Overall there should be no issues.