feat(gfps): Switch to using esp-cpp/nearby (fork of google/nearby)

[finger563]

Description

• Switch submodule google/nearby to be esp-cpp/nearby at tag espp-v1.0.12 which is the same commit we were at in google/nearby

Motivation and Context

Related to #466, we need some additional events / callbacks to fully support subsequent pairing.
This will allow us to more easily add changes to the nearby library and integrate them with our systems.

How has this been tested?

• As part of feat(gfps): Added processing to control non-discoverable advertising … #466.
• Building in CI to ensure nothing breaks

Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Hardware (schematic, board, system design) change
• Software change

Checklist:

• My change requires a change to the documentation.
• I have added / updated the documentation related to this change via either README or WIKI

Software

• I have added tests to cover my changes.
• I have updated the .github/workflows/build.yml file to add my new test to the automated cloud build github action.
• All new and existing tests passed.
• My code follows the code style of this project.

[github-actions]

✅Static analysis result - no issues found! ✅

[Copilot]

Pull Request Overview

This PR switches the Google Fast Pair Service (GFPS) submodule from the original google/nearby repository to a fork maintained by esp-cpp/nearby. The change maintains the same commit history while enabling the team to add custom modifications for better ESP-IDF integration and support for subsequent pairing functionality.

• Replaces the google/nearby submodule with esp-cpp/nearby fork
• Updates submodule URL while maintaining existing path structure