Revise GitHub Developer Program documentation

[MdIbuA]

Updated the GitHub Developer Program documentation to clarify registration benefits and integration examples.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
integrations/concepts/github-developer-program.md	fpt ghec	fpt ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[MdIbuA]

I made it easier for people to understand the doc part

[Sharra-writes]

@MdIbuA These changes are fine and do make the article better, but the owner of the program doesn't actually want us to update the article, because the program is in a transition period where they're trying to figure out how to rework it. I haven't heard anything about it for a while and should probably check in, but I'm afraid I can't accept these changes, since the program is in flux and it's hard to say how it works right now.