fix: #616 Add rule for bcts fom for validityEndDate.

[ianliuwk1019]

#616

• (api): adjust "validityEndDate" return calculation for BCTS FOMs.
• (public): on Details Panel display, use "validityEndDate" from api and remove redundant "validityPeriodEndDate" calculation.
• (public): on Public Notice Panel display, conditionally display "Validity Period" for BCTS FOMs using "commentingClosedDate"

I missed to create one with public notice yesterday so didn't show up in Dev, but this is the case from local:

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.

• api
• admin
• public

Once merged, code will be promoted and handed off to following workflow run.

• Main Merge Workflow

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.

• api
• admin
• public

Once merged, code will be promoted and handed off to following workflow run.

• Main Merge Workflow

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.

• api
• admin
• public

Once merged, code will be promoted and handed off to following workflow run.

• Main Merge Workflow

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.

• api
• admin
• public

Once merged, code will be promoted and handed off to following workflow run.

• Main Merge Workflow

[basilv]

See comments.