Added filtering for buildAutoSendable()

[ThePhoenixFox]

SendableChooser references a map of all of the auto commands
Filter provides access to auto command (const) and auto's path
Allows multiple SendableChooser
Allows commands to be updated to latest in pathplanner/auto directory (regenerateSendableReferences())
Provided wiki info for filtering

[mjansen4857]

Out of curiosity, what's the use case for the regenerateSendableReferences method? Add new autos to the chooser if you manually copy them to the rio or something?

[ThePhoenixFox]

Initially, it generates the map of all of the auto commands that are in "deploy/pathplanner/autos" which get used when someone generates a sendableChooser. The map gets referenced everytime a buildAutoChooser() is called.

If a team uploads new autos or modifies autos without deploying (like filezilla), they can use regenerateSendableReferences() to update the commands that are in the map to match the most recent in filesystem which the sendableChoosers' references. This also affects all previously generated sendableChooser to match to most recent since to the best of my knowledge, map iterators/references don't get invalidated from a insert_or_assign operation.

The map in question:

pathplanner/pathplannerlib/src/main/native/include/pathplanner/lib/auto/AutoBuilder.h

Line 205 in 91a976d

static std::map<std::filesystem::path, frc2::CommandPtr> m_autoCommands;

Also got another commit, the directory filter example isn't correct.

[mjansen4857]

Could you remove the

push:
    branches: [main]

trigger for the publish-docs.yml actions workflow? I want to stop pushing docs updates unless the features in the docs are actually released. I would do it myself but don't want to make you merge main for such a minor change.