Improve Rush plugin authoring documentation

- Remove stale "(experimental)" labels from plugin page titles
- Add lifecycle hooks reference table to creating_plugins.md
- Add service registration API documentation (build cache, cobuild)
- Add code example for tapping specific phased commands
- Update first-party plugins table with 4 missing plugins:
  rush-bridge-cache-plugin, rush-http-build-cache-plugin,
  rush-redis-cobuild-plugin, rush-resolver-cache-plugin

Co-authored-by: iclanton <5010588+iclanton@users.noreply.github.com>

Author: Copilot

websites/rushjs.io/docs/pages/configs/rush-plugin-manifest_json.md

@@ -1,5 +1,5 @@
 ---
-title: rush-plugin-manifest.json (experimental)
+title: rush-plugin-manifest.json
 ---
 
 This is the template for the **rush-plugin-manifest.json** file that is used when

websites/rushjs.io/docs/pages/extensibility/creating_plugins.md

@@ -1,5 +1,5 @@
 ---
-title: Creating Rush plugins (experimental)
+title: Creating Rush plugins
 ---
 
 Rush plugins enable repository maintainers to:
@@ -136,6 +136,51 @@ Example project for this scenario:
 > use the `"associatedCommands"` setting to improve performance by
 > avoiding loading the module when it is not needed.
 
+### Available lifecycle hooks
+
+The [RushSession.hooks](https://api.rushstack.io/pages/rush-lib.rushsession/) object exposes
+[lifecycle hooks](https://api.rushstack.io/pages/rush-lib.rushlifecyclehooks/) that your plugin can
+use to register its handlers. The hook system is based on the
+[tapable](https://www.npmjs.com/package/tapable) framework familiar from Webpack.
+
+| Hook | Type | Description |
+| :--- | :--- | :---------- |
+| `initialize` | `AsyncSeriesHook` | Called before executing any Rush CLI command. |
+| `runAnyGlobalCustomCommand` | `AsyncSeriesHook` | Called before executing any global custom command (defined in command-line.json). |
+| `runGlobalCustomCommand` | `HookMap` | A hook map to target specific named global commands before execution. |
+| `runAnyPhasedCommand` | `AsyncSeriesHook` | Called before executing any phased command (including the default `build` and `rebuild`). |
+| `runPhasedCommand` | `HookMap` | A hook map to target specific named phased commands before execution. |
+| `beforeInstall` | `AsyncSeriesHook` | Called between preparing the common/temp folder and invoking the package manager during `rush install` or `rush update`. |
+| `afterInstall` | `AsyncSeriesHook` | Called after a successful install. |
+| `flushTelemetry` | `AsyncParallelHook` | Allows plugins to process telemetry data. |
+
+For example, to tap a specific phased command:
+
+```ts
+public apply(rushSession: RushSession, rushConfiguration: RushConfiguration): void {
+  rushSession.hooks.runPhasedCommand.for('build').tapPromise(
+    this.pluginName,
+    async (command: IPhasedCommand) => {
+      const logger: ILogger = rushSession.getLogger(this.pluginName);
+      logger.terminal.writeLine('The "rush build" command is about to run!');
+    }
+  );
+}
+```
+
+### Registering service providers
+
+The `RushSession` object also provides methods for plugins that implement build cache or cobuild
+lock providers:
+
+| Method | Description |
+| :----- | :---------- |
+| `registerCloudBuildCacheProviderFactory(name, factory)` | Registers a factory that creates a cloud build cache provider for the given provider name. |
+| `registerCobuildLockProviderFactory(name, factory)` | Registers a factory that creates a cobuild lock provider for the given provider name. |
+
+These are used by plugins such as `@rushstack/rush-amazon-s3-build-cache-plugin` and
+`@rushstack/rush-redis-cobuild-plugin` to integrate with Rush's build cache and cobuild systems.
+
 ### Defining a config file for your plugin
 
 Often a plugin will need to be configured using its own custom settings. Rush's convention

websites/rushjs.io/docs/pages/maintainer/using_rush_plugins.md

@@ -1,5 +1,5 @@
 ---
-title: Using Rush plugins (experimental)
+title: Using Rush plugins
 ---
 
 Rush plugins enable you to:
@@ -110,7 +110,11 @@ The config filename will have the same as the `pluginName`, for example:
 | :------------------------------------------------------------------------------------------------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------- |
 | [@rushstack/rush-amazon-s3-build-cache-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-amazon-s3-build-cache-plugin)         | Cloud build cache provider for Amazon S3                                                                          |
 | [@rushstack/rush-azure-storage-build-cache-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-azure-storage-build-cache-plugin) | Cloud build cache provider for Azure Storage                                                                      |
-| [@rushstack/rush-serve-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-serve-plugin)                                         | (Experimental) A Rush plugin that hooks into action execution and runs an express server to serve project outputs |
+| [@rushstack/rush-bridge-cache-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-bridge-cache-plugin)                           | Bypasses command execution to populate or restore the build cache from an external orchestrator                    |
+| [@rushstack/rush-http-build-cache-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-http-build-cache-plugin)                   | Cloud build cache provider using a generic HTTP endpoint                                                          |
+| [@rushstack/rush-redis-cobuild-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-redis-cobuild-plugin)                         | Cobuild lock provider using Redis for distributed builds                                                          |
+| [@rushstack/rush-resolver-cache-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-resolver-cache-plugin)                       | Generates a resolver cache file to optimize Node.js module resolution                                             |
+| [@rushstack/rush-serve-plugin](https://github.com/microsoft/rushstack/tree/main/rush-plugins/rush-serve-plugin)                                         | Hooks into action execution and runs an Express server to serve project outputs in watch mode                      |
 
 > **NOTE:** The `@rushstack/rush-amazon-s3-build-cache-plugin` and `@rushstack/rush-azure-storage-build-cache-plugin`
 > packages are currently built-in to Rush and enabled automatically. For now, you should NOT register them