Add namespace to secret creation heredoc

[adamrtalbot]

The heredoc for creating a k8s token was missing a namespace, or at least it didn't match the rest of the docs that focus on the tower-nf namespace. This PR adds it so that it matches up.

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	431cba5
🔍 Latest deploy log	https://app.netlify.com/sites/seqera-docs/deploys/67c764c303b67e0008dc0267
😎 Deploy Preview	https://deploy-preview-492--seqera-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[gwright99]

IMO adding an explicit namespace is always a good idea.

If you don't do that, it will either end up in the default namespace (bad) or - if you have customized your kubectl context to default to another namespace - it will go there instead.

IIRC I had this discussion with docs awhile ago on another ticket and there was a deliberate decision to not include it (I dont recall the reason). I'll see if I can dig up the link.

Edit: Here's the link: #133

[adamrtalbot]

If you don't do that, it will either end up in the default namespace (bad) or - if you have customized your kubectl context to default to another namespace - it will go there instead.

When I followed the instructions, I did exactly this and it took me a hot minute to work it out.

[gwright99]

As per my comment in the Conversation tab, this issue has been covered before and the resulting structure was a deliberate decision. Sticking to the sidelines and making no comment re: viability of this PR (despite my personal opinions).

[justinegeffen]

Taking @gwright99's comments into account it would probably make sense to update this doc to better reflect the changes we made to the enterprise content last year. @adamrtalbot, would that work? The change is here: https://github.com/seqeralabs/docs/pull/133/files.