chore: added copilot instructions

[mwkyuen]

No description provided.

[mwkyuen]

@Yukthiw can you review this section?

[mwkyuen]

@bdls-jamal can you review this section? Which pattern do you usually use? I don't want there to be 2 patterns, so I'll keep only the pattern that you are using

[bdls-jamal]

Here is an example of the configuration for the heatmap(same as navigator and other views)

const HeatMap: ViewMetadata<HeatMapViewerData, HeatMapViewerState> = {
  name: 'HeatMap view',
  id: 'heatmap-view',

  icon: () => <HeatMapIcon />,
  description: 'HeatMap Viewer.',
  citation() {
    return <div></div>
  },
  actions: [
    { 
      name: 'Reset Pan/Zoom',
      description: 'Reset the pan and zoom of the viewer',
      icon: <YoutubeSearchedForRoundedIcon />,
      mutation: (prevState) => ({
        ...prevState,
        transform: {
          offset: {
            x: 0,
            y: 0,
          },
          zoom: 1,
        },
      }),
    },
  ]
}

I don't think it matches either of the two options generated by copilot but correct me if I am not understanding correctly.

Also, an actual object must also be created in a separate file like so:
export const viewObject = () => {} and then inside it will have constants for initializing the state, theme, outlet context, useQuery, etc. Should all be outlined in the eplant/Eplant/tutorial.md of staging.