feat: Rename the card to advanced-camera-card (#1873)

Whilst the Frigate support in this card is the best among camera
engines, the name incorrectly suggests that Frigate is a requirement.
Instead, to broaden the appeal, change to more camera agnostic name.
This does not suggest any change in priority, role or support for
Frigate.

This change is likely to be bug prone, due to the size of the rename --
the code contains 1500+ references to "Frigate" most of which make sense
to rename, some which do not, all of which needed human assessment.

- Closes #1298


BREAKING CHANGE: References to `frigate-card` in all kinds of
configuration need to be updated to `advanced-camera-card`. An automated
config upgrade should take care of the majority of usecases (click `Edit
-> Upgrade -> Save`), though may not be perfect.

src/camera-manager/reolink/engine-reolink.ts

@@ -181,7 +181,7 @@ export class ReolinkCameraManagerEngine extends BrowseMediaCameraManagerEngine {
     // First fetch all the Reolink cameras that show up under the media root,
     // that match the expected camera. Some Reolink cameras will not show up
     // here causing errors.
-    // https://github.com/dermotduffy/frigate-hass-card/issues/1723
+    // https://github.com/dermotduffy/advanced-camera-card/issues/1723
     const camerasWithMedia = await this._browseMediaManager.walkBrowseMedias(
       hass,
       [