🐛 Duplicate Test IDs in Proposal details and Review Modal

[kneerose]

Description

• Multiple components are assigned identical testId values, causing conflicts.

Proposal Details

• The same testId is used for both parent and child components, leading to ambiguity in testing.

Review Your Submission

• The "Review Your Submission" modal displays multiple testId values from proposal cards. The modal appears to overlap the proposal list, with the proposal list visible in the background.

Expected Behaviour

• Each component should have a unique testId to ensure accurate identification during testing.
• The "Review Your Submission" modal should not inherit or display testId values from the underlying proposal list, maintaining clear separation between the modal and background elements.

Allure Report

Proposal Details

• 7G_1. Should create a proposal with proper info, action data
• 7G_2. Should create a proposal with proper treasury requests data
• 7G_3. Should create a proposal with proper updates to the constitution data
• 7G_4. Should create a proposal with proper motion of no confidence data
• 7N. Should submit a draft proposal

Review your submission

• 7I_1. Should valid review submission in info action Proposal form
• 7I_2. Should valid review submission in treasury requests Proposal form
• 7I_3. Should valid review submission in updates to the constitution Proposal form
• 7I_4. Should valid review submission in motion of no confidence Proposal form
• 7M_1. Should edit a info action proposal draft
• 7M_2. Should edit a treasury requests proposal draft
• 7M_3. Should edit a updates to the constitution proposal draft
• 7M_4. Should edit a motion of no confidence proposal draft

[kneerose]

@MihajlovicMilos1995, The testIds for the "Review your submission" components are fixed, but the testIds for the proposal details still have issues. Specifically, there are duplicate testIds for parent and child components.

Allure Report

• 7G_1. Should create a proposal with proper info action data

CC: @bosko-m