consider changing the default function for composition getting started guide

[jbw976]

The composition getting started guide currently features function-patch-and-transform as the default tab. We should update this to a more modern function that represents a better UX offered by more capable and powerful functions.

The getting started guide is the first composition experience most new Crossplane users will see, so the default tab choice matters. We currently show multiple composition function options:

• Patch and Transform (current default)
• Python
• Go Templating
• KCL
• Pythonic

After some maintainer discussion, the community download numbers make a compelling case for function-go-templating as the default:

• function-go-templating is among the most downloaded composition functions in crossplane-contrib
• Go templating is a familiar experience for users coming from Helm and other Kubernetes tooling
• It provides a simple, approachable first experience without requiring knowledge of a full programming language or exposing too many function protocol details

Long term we may want to consider Python if we invest further in the SDK and DevEx, but function-go-templating would make a good choice for the time being.

[jonasz-lasut]

Strong thumbs up from me, I've had a lot of conversations during Kubecon with users who have started their compositions with Patch and Transform because it's the default implementation shown in docs and they were overwhelmed with it when the compositions started to grow or they needed to add some logic to it.

[Rishab49]

We need to make the tab element "Templated YAML" as the first element of tab list or just make it the active element by default at its (3rd) position?

[jbw976]

good question! I think it would make the most sense to make "templated yaml" the first element in the tab list as a means to it becoming the default path.

[jbw976]

Fixed in #1080 by @Rishab49, thank you for this contribution! 🙇‍♂️