[Plan] Provide guidance for refactoring existing Ajax API commands

Problem/Motivation

This is a planning issue for documenting how to implement equivalent functionality to our existing ajax commands.

We intend to create a developer guide or "cookbook" that shows how to configure HTMX.

Proposed resolution

Link a documentation issue or comment on why it is not needed for each existing command.

• AddCssCommand
  We will not need this command. Any new CSS added to an HTMX response is added to the requesting page.
• AddJsCommand
  We will not need this command. Any new JS added to an HTMX response is added to the requesting page.
• AfterCommand
• AlertCommand
• AnnounceCommand
• AppendCommand
• BeforeCommand
• ChangedCommand
• CloseDialogCommand
• CloseModalDialogCommand
• CssCommand
• DataCommand
• FocusFirstCommand
• HtmlCommand
• InsertCommand
• InvokeCommand
• MessageCommand
• OpenDialogCommand
• OpenModalDialogCommand
• OpenOffCanvasDialogCommand
• PrependCommand
• RedirectCommand
• RemoveCommand
• ReplaceCommand
• RestripeCommand
• SetDialogOptionCommand
• SetDialogTitleCommand
• SettingsCommand
  We will not need this command. Any new settings added to an HTMX response are added to the requesting page.
• TabledragWarningCommand
• UpdateBuildIdCommand
  We will not need this command. Build ID updates are handled by htmx attributes added conditionally in FormBuilder.
• UpdateSelectionCommand

Remaining tasks

Complete and close all child issues. See the documentation added for refactoring ReplaceCommand for an example.

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet