Standardise terminology for starters

[amandakys]

Introduction

We refer to Kedro starters interchangeably as starters, templates or starter templates.

It would be good to standardise how we refer to them across the CLI and the docs

Design

I propose changing starter to template as it is the more common name for what they are. alternatives could include:

• quickstart
• samples (used by Azure and Google)

This would change the CLI command kedro new --starter=spaceflights to kedro new --template=spaceflights

Rollout

This change can be made as part of the rollout of the new kedro new flow proposed in #2388

[datajoely]

Tangentially, I've always disliked that kedro starter list and kedro new --starter are completely disconnected

[amandakys]

The new kedro new flow proposed in #2388 might address that because it adds a 'select a starter' section to the project initialisation flow with a list of available starters and a short description. Maybe with that we can deprecate kedro starter list

(my-virtual-environment) ➜  kedro new 

Project Template
=============
Choose a project template for your new project. 
- astro-airflow-iris: An Iris dataset example project with a minimal setup for deploying the pipeline on Airflow with Astronomer
- blank: A minimal project template
- pandas-iris: An Iris dataset example using Pandas
- pyspark: Configuration and inistialisation for a PySpark pipeline
- pyspark-iris: An Iris dataset example using PySpark 
- spaceflights: Spaceflights tutorial example code
- standalone-datacatalog: A minimum setup to use Kedro's DataCatalog

 [Select your template]: blank

[DimedS]

Discussed on 18.12.23 during Issue Grooming. We decided not to proceed with that as it appears to be no longer relevant. Additionally, it was not included in the 0.19 release.