[Workshop] Mob Programming of a extended backlog task.

# Workshop Request

## What is the title of your workshop

Mob Programming

## When would this run?
Ideally once per Module to regularly drill in pairing (mobbing) practices. Please place this workshop within the dayplan of one sprint per Tools, Logic, Decomposition, Legacy Code, and Complexity where possible.

Within a dayplan is acceptable to mix this into the afternoons where normally students might lose focus or motivation or (in remote's case) leave the call to do solo work.

## What should be mobbed on?
This aims to extend backlog items. So you must find some backlog work that can be extended, for at least one session of mobbing per module.

If a task cannot be extended well, create a new related task that can be worked on. It must relate to the week's sprint. If you are struggling to make extensions for certain modules, please make a ticket for someone else to pick up + extend your work and submit what you can in this initial ticket.

**Please create one workshop with links out to the various different task options that people can choose depending on where they are in the course.** This makes this workshop reusable across modules and extendable.

## What are the key topics that will be covered in the workshop?

- Using git
- Using branches
- Passing the "driver" role around
- any new viewpoints or tips from volunteers
- using debugger / debugging

Ensure volunteers are reminded of their role in this workshop (as people with industry experience and valuable insights, also not the holder of any particular role - all roles get rotated).

## What knowledge does the trainee need before starting?

- What pair programming is
- how to navigate GitHub when collaborating
- how to use git and use branches
- the prep material for that week's sprint
- the backlog items for that week's sprint (this is an extension of that)

## What are the topics that will **not** be covered in the workshop?

- how to pair programme
- basic git and github operations (push/pull/commit/forking/PRs)

## Any other notes?

These changes were discussed [in a Slack thread](https://codeyourfutur-yov6609.slack.com/archives/C0ALXKX0P39/p1782724218899859)

## Completion

This needs adding to the [workshops repo](https://github.com/CodeYourFuture/CYF-Workshops) and then linked into the relevant day plans in the [curriculum](https://github.com/CodeYourFuture/curriculum).

Review the CYF-Workshops repository and the curriculum's relevant day plans for the Tools, Logic, Decomposition, Legacy Code, and Complexity modules. Create one reusable Mob Programming workshop with links to suitable backlog tasks and link it into the applicable day plans; confirm it covers the listed git, branching, driver rotation, and debugging topics.

Written by the indexing model from the issue text.