Remove Restyle in CML or adjust it to follow airbnb style

[DavidGOrtega]

Having some clear difficulties in having consistency in style, its better to just let the linter speak and refuse the PR if the style does not match the chosen style.

We have to:

• Remove Restyle or make it use our eslint config (I remember that to not be possible)

This will make contributions harder but at least the base source code will follow the same convention.

[0x2b3bfa0]

Existential doubt from #581 (comment), #608 (comment) and #648 (comment) about what is the best approach for accessing optional nested values:

Perlification¹

(item) => {
  const { property: { data = '' } = {} } = item;
  return data.endsWith('text');
}

Abracadabra

(item) =>
  item &&
  item.property &&
  item.property.data &&
  item.property.data.endsWith('text');

Chaining²

(item) => item?.property?.data?.endsWith('text')

---

¹ Works for empty objects, but not for nullish values
² Only valid on Node.js 14+ as per #597

[0x2b3bfa0]

Note: as per #581 (comment), we probably should broaden a bit the scope of the issue title.

[0x2b3bfa0]

Another style topic: #583 (comment)

[0x2b3bfa0]

Speaking about what linters can't detect: how deffensive should we be when writing code that interacts with complex systems we can't control?

• hotfix/Gitlab API detect #468 (comment)
• Unmask catch-all token exceptions #563 (comment)
• Cml runner long job #583 (comment)
• Fix endpoint detection logic, broken on FetchError #608 (comment)

[0x2b3bfa0]

Already using optional chaining 🎉

• Add support for Bitbucket native uploads  #943 (review)

[0x2b3bfa0]

Tracking #1026 (comment)