Clarify that a version bump should only be done when appropriate

Changes to internal dependencies that do not change the API (or the
build product) do not require and should not receive a version bump.

Co-authored-by: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>

src/lineage/templates/clean_template.md

@@ -27,8 +27,11 @@ your project.
 - Remove any of the following that do not apply.
 - These boxes should remain unchecked until the pull request has been approved.
 
-- [ ] Bump version via the `bump_version.sh` script, if this
-      repository is versioned.
+- [ ] Bump major, minor, patch, or pre-release version [as
+      appropriate](https://semver.org/#semantic-versioning-specification-semver)
+      via the `bump_version.sh` script *if* this repository is
+      versioned *and* the changes in this PR [warrant a version
+      bump](https://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api).
 
 ## ✅ Post-merge checklist ##
 

src/lineage/templates/conflict_template.md

@@ -77,8 +77,11 @@ that you must resolve before merging this pull request!
 - Remove any of the following that do not apply.
 - These boxes should remain unchecked until the pull request has been approved.
 
-- [ ] Bump version via the `bump_version.sh` script, if this
-      repository is versioned.
+- [ ] Bump major, minor, patch, or pre-release version [as
+      appropriate](https://semver.org/#semantic-versioning-specification-semver)
+      via the `bump_version.sh` script *if* this repository is
+      versioned *and* the changes in this PR [warrant a version
+      bump](https://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api).
 
 ## ✅ Post-merge checklist ##