5038 bug intervention policies are not described well in simulate

[YohannParis]

• tera-intervention-summary-card.vue: Moving it to its own folder
• tera-intervention-policy-card.vue: Improved the structure and styles, including the removal of unnecessary elements and the addition of a header section.
• tera-intervention-policy-drilldown.vue: Enhanced styles for better visual consistency and added padding to the intervention-settings-section class.

[dgauldie]

@liunelson , doesn't it make more sense for the static strings to read "set parameter beta to 0.6 starting at day 15" instead of "set parameter beta to 0.6 at start time 15 day"

also... is "day" reasonable? I guess once we move to dates and timestamps, we can change...

[YohannParis]

@liunelson , doesn't it make more sense for the static strings to read "set parameter beta to 0.6 starting at day 15" instead of "set parameter beta to 0.6 at start time 15 day"

also... is "day" reasonable? I guess once we move to dates and timestamps, we can change...

We use the words days, because that is what the user sees when creating those interventions, once we do the unit better, we can change that, but that is out of scope from this PR

[dgauldie]

ok, I still think we should change the format of the string... keeping day

[YohannParis]

ok, I still think we should change the format of the string... keeping day

Yes, that has been done already!

[liunelson]

@liunelson , doesn't it make more sense for the static strings to read "set parameter beta to 0.6 starting at day 15" instead of "set parameter beta to 0.6 at start time 15 day"

also... is "day" reasonable? I guess once we move to dates and timestamps, we can change...

"day" is really just a placeholder or default value until the UI gets the time unit from the model AMR. With datetime, then the time unit is still relevant since it seems always helpful to see how much time has elapsed since the starting datetime.