chore: Add conventional commits to PR body of discovery document update

[parthea]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #1313 🦕

[parthea]

@busunkim96 @tswast PTAL

[tswast]

Hooray for better test coverage!

I see from the tests that feat(bigquery) is coming from the summary column, but I don't see in this PR where that is happening. Was it always in the summary and we're just including that in the PR body now?

[parthea]

Hooray for better test coverage!

I see from the tests that feat(bigquery) is coming from the summary column, but I don't see in this PR where that is happening. Was it always in the summary and we're just including that in the PR body now?

Correct! It's already included in the summary. The reason that I included it previously was because I also used conventional commit messages in the individual commits for each API. For example, see this commit which has a commit message that begins with feat(admin): update the api.

[parthea]

@busunkim96 PTAL

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.