Filings UI: finish implementation (AGM Extension)

[severinbeauvais]

The framework for this filing was implemented in #11436. This ticket is to complete the filing.

• change FF from enable-agm-extension to supported-agm-extension-entities
• enable allowable actions check (remove debugging)
• update tooltip in case business is NIGS (see how AGM Location did it)
• update menu tooltip not needed
• add help content
• fetch "date of last extension grant on record" from business record obsolete
• add "About the Business" sub-component from ticket Filings UI - "About the Business" sub-component #18272
• add "Extension Request" sub-component from ticket Filings UI - "Extension Request" sub-component #18273
• add "AGM Extension Evaluation" sub-component from ticket Filings UI - "AGM Extension Evaluation" sub-component #18369
• pre-populate Certify legal name with logged in user except if staff
  • always editable
  • see what Filings UI - AGM Location filing (part II) #18161 did for this
• implement new dialog if not eligible for extension
• change dialog to new style/theme
• show dialog if not eligible and user presses File button
• verify fee codes (AGMDT)
• remove save/resume and associated dialogs, methods, etc
• remove staff payment dialog, etc (same as this commit)
• file AGM extension data
  • see Schema (AGM Extension) #17928 for fields
  • done in Filings UI - update dashboard (To do + Filings History List) #18274
• implement unit tests (not including eligibility logic) was ticket Filings UI - update unit tests #18278
• hook up everything (validation, etc)
• delete debugging code

[severinbeauvais]

@seeker25 @argush3
If payment failed then the filing is left in the To Do list in pending status. I think this can only be due a BE error (since this is $0 payment). Will the BE automatically recover from this or does the user need to do something?

[severinbeauvais]

"Time to hold AGM" table / function:

[severinbeauvais]

@riyazuddinsyed This ticket has changes in Release 19.5a, and will have changes in a further release. This is why it is tagged to this release but is in the sprint backlog still.

[yuisotozaki]

Observation:
There is a calculation error when a first AGM is extended twice in a row.

• Incorporation date: Sept 7, 2023
• First extension due date: March 7, 2025 (correct)
• Second extension due date: March 7, 2027 (incorrect - this should be Sept 7, 2025). The second extension does not file. It errors out with "Failed to load resource: the server responded with a status of 400 (BAD REQUEST)" at https://legal-api-dev.apps.silver.devops.gov.bc.ca/api/v2/businesses/BC0871463/filings:1

EDIT: This will be covered in a bug ticket. The rest if ready for QA.