feat: add new privacy type

[ChaituVR]

Summary

• Adds new option in space settings to select "any" privacy type
• Adds new option on proposal editor to enable/disable shielded voting
• Adds new option on update proposal editor to enable/disable shielded voting

Closes: https://github.com/snapshot-labs/workflow/issues/277

How to test

2. Go to your settings, under Privacy - you should see the new option "any"

3. Inside proposal editor, you should see new option
   

4. Try create a new proposal with/without shutter
5. Try updating proposal with/without shutter

[ChaituVR]

Comments:

• Default to Any
• Any should be the first option in the list

[bonustrack]

Just tested and the design looks good

Copilot reviewed 5 out of 20 changed files in this pull request and generated no suggestions.

Files not reviewed (15)

• apps/ui/src/components/FormSpaceVoting.vue: Evaluated as low risk
• apps/ui/src/components/Modal/SelectPrivacy.vue: Evaluated as low risk
• apps/ui/src/views/Space/Editor.vue: Evaluated as low risk
• apps/ui/src/views/Proposal/Overview.vue: Evaluated as low risk
• apps/ui/src/composables/useActions.ts: Evaluated as low risk
• packages/sx.js/src/types/index.ts: Evaluated as low risk
• packages/sx.js/src/clients/offchain/types.ts: Evaluated as low risk
• apps/ui/src/helpers/constants.ts: Evaluated as low risk
• packages/sx.js/src/clients/offchain/ethereum-sig/types.ts: Evaluated as low risk
• apps/ui/src/networks/starknet/actions.ts: Evaluated as low risk
• apps/ui/src/networks/types.ts: Evaluated as low risk
• apps/ui/src/networks/offchain/api/index.ts: Evaluated as low risk
• apps/ui/src/networks/evm/actions.ts: Evaluated as low risk
• apps/ui/src/networks/common/graphqlApi/index.ts: Evaluated as low risk
• apps/ui/src/networks/offchain/actions.ts: Evaluated as low risk

Comments skipped due to low confidence (1)

apps/ui/src/composables/useSpaceSettings.ts:164

• [nitpick] The use of an empty string ('') as a valid value for the privacy field might be ambiguous. Consider using a more descriptive value or ensure that its use is well-documented.

const privacy = ref<'' | 'shutter' | 'any'>('');

[Sekhmet]

It look good to me, maybe only thing that I'd change is avoid using "" as a value with meaning (like before we had "none" for this that got converted at the edge when storing/retrieving settings). Any reason we ended up introducing it (other than to make it match offchain space settings)?

I'd rather keep clearer values like "none" | "any" | "shutter".

[Sekhmet]

Maybe instead od modifying existing test case we should add new one for shutter privacy (the rest can stay the same).

[Sekhmet]

Looks like it doesn't matter there, but if space has configured Shielded voting privacy, and you submit proposal privacy will be ''.

I tested it and proposal still ends up using Shutter, but it's a bit confusing.

[ChaituVR]

with out privacy we need to pass this type on a condition 🙈 will add a layer of confusion

maybe we should just pass shutter by default if space uses shutter?