Cherry pick documentation for ROCm 6.3

[bstefanuk]

This PR cherry picks the following commits into the docs/6.3 branch:

• 09ec347
• 7ac8e75
• 9b35483

[SwRaw]

Tensile contribution guidelines

[bstefanuk]

Placing "Tensile" in front of every title is redundant and potentially misleading since the term is overloaded in the project.

If SEO is the goal, there are alternatives I would prefer prioritizing such as placing keywords naturally into the body of the text, getting backlinks from other sites, using strong internal linking, etc. Either way, I don't think the usage of "Tensile" is overlooked for this site, it's already mentioned >200 times in the docs/src directory.

[SwRaw]

Suggested change

	Programmer's guide
	Tensile programmer's guide

[SwRaw]

Suggested change

	Installation
	Tensile installation

[SwRaw]

Suggested change

	Environment variables
	Tensile environment variables

[SwRaw]

@bstefanuk Can we add the content from Introduction into index.rst? The introduction file shouldn't be required as a separate entity.

[bstefanuk]

@SwRaw I like having a document to introduce the concepts in Tensile, so I would prefer to keep it. We can add more content to it to make it a more meaningful standalone document, if it makes sense.

[SwRaw]

Suggested change

	Tensile is a tool for creating a benchmark-driven backend library for General Matrix-Matrix Multiplications (GEMMs), GEMM-like problems such as batched GEMM, N-dimensional tensor contractions, and anything else that multiplies two multidimensional objects together on an AMD GPU.
	Tensile is a tool for creating a benchmark-driven backend library for General Matrix-Matrix Multiplications (GEMMs), GEMM-like problems such as batched GEMM, N-dimensional tensor contractions, and anything else that multiplies two multidimensional objects together on an AMD GPU.
	Tensile is written in Python for library and kernel generation and in C++ for client headers and library tests. It is a vital
	project in the ROCm ecosystem, providing optimized kernels for downstream libraries such as :doc:`rocBLAS <rocblas:index>`.
	The parts of Tensile that are written in Python consist of applications that are collectively responsible
	for generating optimized kernels and library objects to access these kernels from client code.

[SwRaw]

Suggested change

	Solution selection catalogs
	Tensile's solution selection catalogs

[SwRaw]

Suggested change

	Tensile provides a mechanism by which only a subset of the code object files produced during a build are loaded at runtime.
	This is necessary to avoid the overhead associated with loading code object files including initialization time and the
	memory footprint of the loaded code object files. However, this introduces the problem of knowing which code object file to load.
	To avoid the overhead associated with loading code object files including initialization time and the
	memory footprint of the loaded code object files, Tensile provides a mechanism to load only a subset of the code object files produced during a build, at runtime.
	To achieve this, it must be determined which code object file to load.

[SwRaw]

Suggested change

	Solution selection is the process by which the **TensileHost** library determines what kernel is preferred and, in turn,
	what code object file contains the selected kernel. This process uses a hierarchical structure
	to efficiently search for kernels based on hardware, problem size, and transpose, among others.
	To determine the preferred kernel and the code object file containing the selected kernel, the ``TensileHost`` library utilizes a process named `Solution selection`. This process uses a hierarchical structure to efficiently search for kernels based on hardware, problem size, and transpose, among others.

[SwRaw]

Suggested change

	This is the role of the **solution selection catalog** [1]_---a serialized file that uses a hierarchical
	schema to organize kernel metadata for efficient lookup at runtime.
	For efficient lookup at runtime, the kernel metadata must be organized in a hierarchical schema in a serialized file named `solution selection catalog` [1]_.

[SwRaw]

@bstefanuk Why are [_C], [_B], [_A] needed? Remove them if not referenced.

[bstefanuk]

Visual helper to show opening and closing of sections. There could be a better way to do this. They are referenced below.

[SwRaw]

@bstefanuk Why underscore after A, B, C?

[SwRaw]

Suggested change

	Line **[A]** shows the top level of the parent catalog, which contains a single row for each hardware architecture.
	Line **[B]** shows the problem map for the operation *Contraction_l_Alik_Bjlk_Cijk_Dijk*.
	Line **[C]** shows the problem type and predicates used to match against exact solutions contained in the child catalogs.
	Note that the lines in the parent catalog are marked as A,B, and C for reference.
	- Line [A]: Shows the top level of the parent catalog, which contains a single row for each hardware architecture.
	- Line [B]: Shows the problem map for the operation *Contraction_l_Alik_Bjlk_Cijk_Dijk*.
	- Line [C]: Shows the problem type and predicates used to match against exact solutions present in the child catalogs.

[SwRaw]

@bstefanuk Why are we documenting the mode, which is not recommended and on the verge of deprecation.

[bstefanuk]

Because it's still demonstrative of the purpose and history of the catalogs.

[SwRaw]

Suggested change

	.. [1] Previously these files were called *master solution libraries* because they contain two top level keys, "solutions" and "library". The term *solution selection catalog* was later adopted to clarify the purpose of this file within the larger context of the Tensile C++ API.
	.. [1] Previously these files were named *master solution libraries* because they consisted of two top-level keys, "solutions" and "library". The term *solution selection catalog* was later adopted to clarify the purpose of this file within the larger context of the Tensile C++ API.

[SwRaw]

Suggested change

	This topic lists and describes the frequently used terms in the Tensile documentation.

[SwRaw]

Suggested change

	General matrix multiplication (GEMM) is a level 3 BLAS operation that computes the product of two matrices, formalized by the equation,
	General matrix multiplication (GEMM) is a level 3 BLAS operation that computes the product of two matrices, formalized by the following equation:

[SwRaw]

Suggested change

	where :math:`\alpha` and :math:`\beta` are scalars and :math:`A` and :math:`B` are optionally transposed input matrices.
	In the given formula, :math:`\alpha` and :math:`\beta` are scalars and :math:`A` and :math:`B` are optionally transposed input matrices.

[SwRaw]

Suggested change

	* - 3 Batched Indices
	* - 3 Batched indices

[SwRaw]

Suggested change

	* - 4 Free Indices
	* - 4 Free indices

[SwRaw]

Suggested change

	**Tensile only supports problems with at least one pair of free indices.**
	.. note::
	Tensile only supports problems with at least one pair of free indices.

[SwRaw]

@SwRaw I like having a document to introduce the concepts in Tensile, so I would prefer to keep it. We can add more content to it to make it a more meaningful standalone document, if it makes sense.

@bstefanuk I have added the content from introduction into index.rst and prefer to remove introduction file. Once we have enough content , we can plan something for later. Right now, its better to include the introduction on the index page.

[bstefanuk]

Comments on this branch are captured in #2056 and include largely changes of taste. Moving forward with merge for 6.3 docs.