[AV-60739] Attributes for Day 0 Docs

[sarahlwelton]

Adding necessary {db} and {cptl-db} attributes to playbooks for building docs after Day 0 updates.

Will make the future transition onto "operational database" much easier, if that ends up being the final decision.

[osfameron]

As someone who has enjoyed figuring out what attributes like {sgw-te} and {cblFrmWk} in Mobile mean, I'm excited about everyone else getting the opportunity to participate in the fun!

(Don't mean to snark, I've perpetrated enough of these myself... anyway, seeing it in a PR makes me wonder if we should try to do something about it and maybe come up with some best practices ongoing.)

e.g. What does cptl mean? Can we spell it out in full?
Or is it worth adding YAML comments, like e.g.:

db: cluster # the name of a "database-like-thing"

[RichardSmedley]

Could be listed in the README?

(I'm in the process of doing just that for SDK Docs' own growing list of attributes)

[sarahlwelton]

I was trying to keep it short for the sake of easy typing in running doc.

If we'd rather spell it out for explicitness, I'm okay with that.

[lamagnifica]

an inline comment would be wonderful from my PoV

[lamagnifica]

@sarahlwelton do we need to start with tokens for both database and cluster? or product-specific tokens?
Capella uses cluster in the APIs and database in the UI to mean the same object.
Capella columnar services uses cluster for, essentially, the same object again, in both the API and the UI.

Rumor is that eventually, in Capella database will be replaced with operational database, but the API will continue to use cluster.
In sum, "cluster" is a valid term, and "database" is a valid term, and the only potential change coming is "database" to "operational database".
I think that adding only a single token now for cluster, and naming it {db}, is going to be problematic.