.cci.Jenkinsfile: don't use dev profile for CI testing

The debug binaries are much larger and we were running out of
space in some tests such as the `ext.config.rpm-ostree.kernel-replace`
test.

Use the release profile here which creates much smaller binaries.

Author: dustymabe

.cci.jenkinsfile

@@ -9,7 +9,7 @@ buildPod {
     checkout scm
 
     stage("Build") {
-        shwrap("make && make install DESTDIR=install")
+        shwrap("make RELEASE=1 && make install RELEASE=1 DESTDIR=install")
         stash name: 'build', includes: 'install/**'
     }
 }

Makefile

@@ -8,7 +8,7 @@ ifeq ($(RELEASE),1)
 else
 	PROFILE ?= debug
 	CARGO_ARGS = --features docgen
-	# In debug mode (most often used by devs/CI), we default to stripping
+	# In debug mode (most often used by devs), we default to stripping
 	# `rdcore` because it's otherwise huge and in kola's default 1G VMs can
 	# cause ENOSPC. In release mode (most often used by Koji/Brew), we don't do
 	# this because the debuginfo gets split out anyway. In either profile,

docs/release-notes.md

@@ -15,6 +15,7 @@ Minor changes:
 Internal changes:
 
 - Add initial TMT tests and a new workflow to execute tests on PRs
+- Use release profile for smaller binaries in CI testing
 
 Packaging changes: