This causes a crash under Ruby 3.3, and it does not seem necessary.

e.g. logs where the host ran out of disk space don't have Version:,
Status:, or Build-Time: lines.

Keep the later one since it sets the value of `chroot` while the former
doesn't.

sbuild logs downloaded from buildd.debian.org have an extra empty line
at the beginning. In any case, leading whitespace is pointless in logs.

Several of those templates were obsolete (mentioning lenny, jessie).
Keep one single template for generic FTBFS bugs, all other cases can be
handled by custom templates in the command line.

New templates for bugtypes can be added by creating
lib/collab-qa/bug_templates/${BUGTYPE}.txt.liquid

The template is using Liquid, which is similar to Smarty(PHP) and
Jinja2(Python). Example template I'm using for ruby3.0 FTBFS triaging:

----------------8<----------------8<----------------8<-----------------
From: {{ fullname }} <{{ email }}>
To: submit@bugs.debian.org
Subject: {{ package }}: FTBFS with ruby3.0: {{ summary }}

Source: {{ package }}
Version: {{ version | split:'+rebuild' | first }}
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-ruby@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, {{ package }} was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
{% for line in extract %}> {{ line }}
{% endfor %}

The build full is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/{{ package }}/{{ filename | replace:".log",".build.txt" }}
----------------8<----------------8<----------------8<-----------------