fix(sns): Pass additional_critical_native_action_ids in SNS initialization flow

[jasonz-dfinity]

Why

In the previous PR #8686 a new field additional_critical_native_action_ids was added to SNS. However, it wasn't added to SnsInitPayload so it was not passed through the NNS Governance => SNS W => SNS Governance in the initialization flow.

What

• Add a pocket IC test:
  • Tests the initialization flow - an SNS initialized with the action ids have additional critical proposal types
  • Tests updating of the list - the SNS can still remove critical proposal types afterwards
  • This test fails (as expected) without the fix in the second commit
• Add the new field to SnsInitPayload, and implement the conversions CreateServiceNervousSystem=>SnsInitPayload=>NervousSystemParameters

[github-actions]

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

1. Update unreleased_changelog.md (if there are behavior changes, even if they are
   non-breaking).

2. Are there BREAKING changes?

3. Is a data migration needed?

4. Security review?

How to Satisfy This Automatic Review

1. Go to the bottom of the pull request page.

2. Look for where it says this bot is requesting changes.

3. Click the three dots to the right.

4. Select "Dismiss review".

5. In the text entry box, respond to each of the numbered items in the previous
   section, declare one of the following:

• Done.

• $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
  canister behavior changes.", or for item 2, "Existing APIs
  behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

1. No need as the previous PR already added one
2. Not breaking
3. No impact on existing data
4. No need