WIP 1844 Part 1: auto-generated human-IDs and aliases

[martin-lysk]

This PR introduces auto-generated human-IDs and aliases behind the experimental: aliases flag.

For background, please see #1892 and #1844 (comment) and the message docs.

This PR also adds file-system-based locking to improve the behavior of concurrent message updates through the load/store plugin api. Most of these change are in loadProject.

In order to validate these changes, there is also a new sdk/load-test, and a mock machine translate api.

tasks

• feature flag for human ids and aliases
• enable feature flag for opral projects
• add message.alias (non-optional) property
• autogenerate human ids and set alias = plugin id on load
• message file locking on load/save, read/write
• validate file locking (should fix [bug] Can't machine-translate multiple new keys #1968)
• validate with large project
• add mock translation to rpc
• add test for file locking with real FS and mock translation
• uncomment cli translate progress bar or make it optional
• replace console logs with debug logger flag
• fink.
  • show aliases alongside message ids
  • seach messages by alias
• ide-extension
  • recognize message aliases returned by matchers.
  • show aliases in inlang tab (design tbd)
  • (separate PR) auto-generate human ids for new (e.g. extracted) messages
• paraglide
  • compile aliases into message functions
  • generate deprecation comments for aliases
• add SDK docs for aliases and human IDs
• revisit TODOs
• PR review
• changeset
• 🚢

...onward to 1844 Part 2: inlang message persistence

human ids (opral only)

Message ids from a plugin are replaced with human ids derived from the message id. The id becomes the default alias.

Existing message references in code may continue to use the plugin id, now stored in the default alias. A new api messages.getByDefaultAlias() resolves aliases e.g. when matched by the ide-extension:

const highlightedMessages = matchedMessages
  // resolve messages from id or alias
  .map((message) => {
    return (
      state().project.query.messages.get({ where: { id: message.messageId } }) ??
      state().project.query.messages.getByDefaultAlias(message.messageId)
    )
  })

In fink, the alias is shown alongside the human id

the ide-extension checks for aliases as well as ids when it matches references to messages

The message.alias is a non-optional property of the message api. NOTE: This change to the TypeScript Message interface impacts a large number of tests. Additional modification was required in those tests which expect to be able to get() messages using the original message key.

[martin-lysk]

Some followup comments - but we are getting there