feat!: remove three templates

These templates required additional fields, but licenses
itself are not very popular, so I decided to drop support
for them instead implementing additional functions.

internal/templates/BSD-4-Clause.tmpl

@@ -1,61 +0,0 @@
----
-title: BSD 4-Clause "Original" or "Old" License
-spdx-id: BSD-4-Clause
-
-description: A permissive license similar to the <a href="/licenses/bsd-3-clause/">BSD 3-Clause License</a>, but with an "advertising clause" that requires an acknowledgment of the original source in all advertising material.
-
-how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace {{ .Year }} with the current year and {{ .AuthorName }} with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work.
-
-using:
-  Choco-solver: https://github.com/chocoteam/choco-solver/blob/master/LICENSE
-  PMSPAUR-public: https://github.com/ArthurGodet/PMSPAUR-public/blob/master/LICENSE
-  Switchblade: https://github.com/SwitchbladeBot/switchblade/blob/dev/LICENSE
-
-permissions:
-  - commercial-use
-  - modifications
-  - distribution
-  - private-use
-
-conditions:
-  - include-copyright
-
-limitations:
-  - liability
-  - warranty
-
----
-
-BSD 4-Clause License
-
-Copyright (c) {{ .Year }}, {{ .AuthorName }}
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-1. Redistributions of source code must retain the above copyright notice, this
-   list of conditions and the following disclaimer.
-
-2. Redistributions in binary form must reproduce the above copyright notice,
-   this list of conditions and the following disclaimer in the documentation
-   and/or other materials provided with the distribution.
-
-3. All advertising materials mentioning features or use of this software must
-   display the following acknowledgement:
-     This product includes software developed by [project].
-
-4. Neither the name of the copyright holder nor the names of its
-   contributors may be used to endorse or promote products derived from
-   this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY COPYRIGHT HOLDER "AS IS" AND ANY EXPRESS OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
-EVENT SHALL COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
-PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
-OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
-WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
-OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

internal/templates/NCSA.tmpl

@@ -1,63 +0,0 @@
----
-title: University of Illinois/NCSA Open Source License
-spdx-id: NCSA
-nickname: UIUC/NCSA
-
-description: The University of Illinois/NCSA Open Source License, or UIUC license, is a permissive free software license, based on the <a href="/licenses/mit/">MIT/X11 license</a>  and the <a href="/licenses/bsd-3-clause/">BSD 3-clause License</a>. Its conditions include requiring the preservation of copyright and license notices both in source and in binary distributions and the prohibition of using the names of the authors or the project organization to promote or endorse derived products.
-
-how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace {{ .Year }} with the current year and {{ .AuthorName }} with the name (or names) of the copyright holders. Replace {{ .Organization }} with the project organization, if any, that sponsors this work.
-
-using:
-  ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt
-  RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE
-  ToaruOS: https://github.com/klange/toaruos/blob/master/LICENSE
-
-permissions:
-  - commercial-use
-  - modifications
-  - distribution
-  - private-use
-
-conditions:
-  - include-copyright
-
-limitations:
-  - liability
-  - warranty
-
----
-
-University of Illinois/NCSA Open Source License
-
-Copyright (c) {{ .Year }} {{ .AuthorName }}. All rights reserved.
-
-Developed by: {{ .Organization }}
-              {{ .AuthorName }}
-              {{ .URL }} 
-
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation files
-(the "Software"), to deal with the Software without restriction,
-including without limitation the rights to use, copy, modify, merge,
-publish, distribute, sublicense, and/or sell copies of the Software,
-and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-* Redistributions of source code must retain the above copyright notice,
-  this list of conditions and the following disclaimers.
-
-* Redistributions in binary form must reproduce the above copyright
-  notice, this list of conditions and the following disclaimers in the
-  documentation and/or other materials provided with the distribution.
-
-* Neither the names of {{ .AuthorName }}, [project] nor the names of its
-  contributors may be used to endorse or promote products derived from
-  this Software without specific prior written permission.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH
-THE SOFTWARE.

internal/templates/Vim.tmpl

@@ -1,111 +0,0 @@
----
-title: Vim License
-spdx-id: Vim
-
-description: There are no restrictions on using or distributing an unmodified copy of the software. Parts of the software may also be distributed, but the license text must always be included. For modified versions a few restrictions apply. The license is GPL compatible, you may compile the software with GPL libraries and distribute it.
-
-how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [project] with the project name.
-
-using:
-  Vim: https://github.com/vim/vim/blob/master/LICENSE
-  Pathogen: https://github.com/tpope/vim-pathogen/blob/master/LICENSE
-  vim-license-gen: https://github.com/othree/vim-license/blob/master/LICENSE
-
-permissions:
-  - commercial-use
-  - modifications
-  - distribution
-  - private-use
-
-conditions:
-  - include-copyright
-  - document-changes
-  - disclose-source
-  - same-license
-
-limitations: []
-
----
-
-VIM LICENSE
-
-I)  There are no restrictions on distributing unmodified copies of [project]
-    except that they must include this license text.  You can also distribute
-    unmodified parts of [project], likewise unrestricted except that they must
-    include this license text.  You are also allowed to include executables
-    that you made from the unmodified [project] sources, plus your own usage
-    examples and Vim scripts.
-
-II) It is allowed to distribute a modified (or extended) version of [project],
-    including executables and/or source code, when the following four
-    conditions are met:
-    1) This license text must be included unmodified.
-    2) The modified [project] must be distributed in one of the following five
-       ways:
-       a) If you make changes to [project] yourself, you must clearly describe
-          in the distribution how to contact you.  When the maintainer asks
-          you (in any way) for a copy of the modified [project] you
-          distributed, you must make your changes, including source code,
-          available to the maintainer without fee.  The maintainer reserves
-          the right to include your changes in the official version of
-          [project].  What the maintainer will do with your changes and under
-          what license they will be distributed is negotiable.  If there has
-          been no negotiation then this license, or a later version, also
-          applies to your changes. The current maintainer is Bram Moolenaar
-          <Bram@vim.org>.  If this changes it will be announced in appropriate
-          places (most likely vim.sf.net, www.vim.org and/or comp.editors).
-          When it is completely impossible to contact the maintainer, the
-          obligation to send him your changes ceases.  Once the maintainer has
-          confirmed that he has received your changes they will not have to be
-          sent again.
-       b) If you have received a modified [project] that was distributed as
-          mentioned under a) you are allowed to further distribute it
-          unmodified, as mentioned at I).  If you make additional changes the
-          text under a) applies to those changes.
-       c) Provide all the changes, including source code, with every copy of
-          the modified [project] you distribute.  This may be done in the form
-          of a context diff.  You can choose what license to use for new code
-          you add.  The changes and their license must not restrict others
-          from making their own changes to the official version of [project].
-       d) When you have a modified [project] which includes changes as
-          mentioned under c), you can distribute it without the source code
-          for the changes if the following three conditions are met:
-          - The license that applies to the changes permits you to distribute
-            the changes to the Vim maintainer without fee or restriction, and
-            permits the Vim maintainer to include the changes in the official
-            version of [project] without fee or restriction.
-          - You keep the changes for at least three years after last
-            distributing the corresponding modified [project].  When the
-            maintainer or someone who you distributed the modified [project]
-            to asks you (in any way) for the changes within this period, you
-            must make them available to him.
-          - You clearly describe in the distribution how to contact you.  This
-            contact information must remain valid for at least three years
-            after last distributing the corresponding modified [project], or
-            as long as possible.
-       e) When the GNU General Public License (GPL) applies to the changes,
-          you can distribute the modified [project] under the GNU GPL version
-          2 or any later version.
-    3) A message must be added, at least in the output of the ":version"
-       command and in the intro screen, such that the user of the modified
-       [project] is able to see that it was modified.  When distributing as
-       mentioned under 2)e) adding the message is only required for as far as
-       this does not conflict with the license used for the changes.
-    4) The contact information as required under 2)a) and 2)d) must not be
-       removed or changed, except that the person himself can make
-       corrections.
-
-III) If you distribute a modified version of [project], you are encouraged to
-     use the Vim license for your changes and make them available to the
-     maintainer, including the source code.  The preferred way to do this is
-     by e-mail or by uploading the files to a server and e-mailing the URL. If
-     the number of changes is small (e.g., a modified Makefile) e-mailing a
-     context diff will do.  The e-mail address to be used is
-     <maintainer@vim.org>
-
-IV)  It is not allowed to remove this license from the distribution of the
-     [project] sources, parts of it or from a modified version.  You may use
-     this license for previous [project] releases instead of the license that
-     they came with, at your option.
-
-