Improve readability of DP best practices

[digitaldiina]

Is there an existing issue for this?

• [X] I have searched the existing issues

What kind of idea is it?

Add or revise existing page

Who is it for?

Developer

Which area (SuperOffice entity) is this related to?

Other

Description

The best practices page in the developer portal docs is hard to digest.

Consider splitting it in multiple sub-pages. Give examples

[ejfasting]

I suggest the following:

• [ ] Remove Tenant availability, this is duplicate of sub-page Tenant status? At least migrate documentation over to the sub-page and reference it in index.md.
• [ ] Remove How to check status sub-page, as its duplicate of Tenant status.
• [ ] Rename Credential manager to "Ticket/Token expiration". Move to sub-page (?) and reference external (Microsoft?) documentation for 'Sliding expiration'.
• [ ] Create sub-page for Api usage
• [ ] Create sub-page for Count. Possibly rename to something general (Filters/query-optimizations?) and include Use filters and Optimization
• [ ] Create sub-page for webhooks and move webhooks and tenant status webhook.
• [ ] Create sub-page for Logging
• [ ] Create sub-page for Searching
• [ ] Reference the new sub-pages in index.md

'Best practices' contains a lot of valuable information, but not everything is related to the Developer portal itself.. We could consider moving, for example, Searching to Api (?)