Record soft failure when encountering unexpected situations

- If we're online but still get release notes from RPM then we
  just soft-fail.
- Soft failure will have a reference to poo#97316

schedule/yast/skip_registration/offline_install+skip_registration.yaml

@@ -4,7 +4,7 @@ description:    >
   Offline installation. Skipping registration for SLE 15, as requires network connection.
   This is default behavior for SLE 12.
 vars:
-  SCC_REGISTER: 'none'
+  SCC_REGISTER: 'installation'
   ADDONS: all-packages
 schedule:
   - installation/bootloader_start
@@ -13,6 +13,7 @@ schedule:
   - installation/network_configuration
   - installation/scc_registration
   - installation/addon_products_sle
+  - installation/releasenotes_origin
   - installation/system_role
   - installation/partitioning
   - installation/partitioning_finish

tests/installation/releasenotes_origin.pm

@@ -25,7 +25,7 @@ sub run {
     enter_cmd "grep -o \"Got release notes.*\" /var/log/YaST2/y2log";
     assert_screen [qw(got-releasenotes-RPM got-releasenotes-URL)];
     unless (match_has_tag "got-releasenotes-$src") {
-        die "Release notes source does NOT match expectaions or not found in YaST logs, expected source: $src";
+        record_soft_failure("poo#97316: Release notes source does NOT match expectations or not found in YaST logs, expected source: $src");
     }
     enter_cmd "exit";
     # If we don't have system role screen, release notes origin is verified on partitioning screen