add license key information to installation instructions

[doy-materialize]

Motivation

https://github.com/MaterializeInc/database-issues/issues/9675

Tips for reviewer

this adds information to the installation and upgrade guides. we'll still want to also add information to the 25.3 release notes once we have a page for those.

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[kay-kim]

Could we add this blurb to a file in doc/user/shared-content/ ?

Then, all we need to do in the various files is
{{< include-md file="shared-content/filename.md" >}}

[doy-materialize]

does this look right? i'm not sure how to build/preview the docs

[kay-kim]

To build/preview ...

• locally, if you go to the ... doc/user directory and run

hugo server --disableFastRender --ignoreCache  --baseURL http://localhost:1313/docs/ 

You'll see the following

In the PR, we automatically build the preview at https://preview.materialize.com/materialize/<PR NUM>/

[kay-kim]

Could we also update:

• https://materialize.com/docs/license/#materialize-self-managed

• https://github.com/MaterializeInc/materialize/blob/main/doc/user/shared-content/self-managed/install-landing-page.md

[kay-kim]

For release notes, you can add them to doc/user/content/releases/_index.md

See
https://github.com/MaterializeInc/materialize/pull/33978/files/c7c032e54d78835185eb7619d8e705b2589bde39#diff-d01957d4b77e445f01111af28bbcf368abee8d9742748e696f7f3fd74f6e083c

[kay-kim]

QQ: How do new enterprise customers get the license key? Like once a new customer purchases an enterprise license ... what is the mechanism by which they get their key?

[kay-kim]

That is, should we blurb a generic sentence w.r.t. enterprise customers?

[kay-kim]

Kind of like "If you have purchased an Enterprise License, your license key can be obtained blah..."

[doy-materialize]

i think that's still kind of up in the air - for now, i think we're just going to generate them internally and email them to users or something along those lines. i think we can update the docs later once we have a better idea of what the workflow will look like.

[maheshwarip]

For enterprise license keys: we can just say "contact us to receive your enterprise license key".