chore: add snap for ubuntu

[SamirPS]

What this PR does / why we need it:

This PR permit to create a snap for ubuntu.

On Linux install snapcraft

 sudo snap install snapcraft --classic

git clone this repository and put the snapcraft.yaml file i put on the PR in this folder.

And After

 snapcraft --debug

AT the end you will have a .Snap file install it with

 sudo snap install *.snap  --dangerous

You have installed the snap, now just run oras by typing oras

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Please check the following list:

• Does the affected code have corresponding tests, e.g. unit test, E2E test?
• Does this change require a documentation update?
• Does this introduce breaking changes that would require an announcement or bumping the major version?
• Do all new files have an appropriate license header?

[codecov-commenter]

Codecov Report

Merging #965 (71e74a5) into main (57005b9) will not change coverage.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main     #965   +/-   ##
=======================================
  Coverage   81.15%   81.15%           
=======================================
  Files          53       53           
  Lines        2776     2776           
=======================================
  Hits         2253     2253           
  Misses        354      354           
  Partials      169      169           

[TerryHowe]

/lgtm

[qweeah]

Thanks @SamirPS for contributing. Should snapcraft --debug be added to Github actions so the snap of ORAS can be automatically updated when releasing?

[SamirPS]

@qweeah you can use theses actions to build and publish :

https://github.com/snapcore/action-build and https://github.com/snapcore/action-publish

[qweeah]

nit: can you help format the header as suggested, thanks

[qweeah]

Another stupid question on the versioning: I followed the instructed steps and the snapcraft ends with generating a file named oras_v0.8.1+git377.3792315_amd64.snap. What does the v0.8.1 mean? I think this is not the version of built ORAS since I then do snap install and the generated version of oras is 1.0.0+unreleased.

[SamirPS]

It's not the version of oras it's come from the version:git name the snap like this oras_$(git_describe)_$(arch).snap

[qweeah]

LGTM

[shizhMSFT]

LGTM

[shizhMSFT]

@SamirPS Ready to be merged?

[SamirPS]

Not for now @shizhMSFT we have a little issue when registering the name oras with @FeynmanZhou

[SamirPS]

@shizhMSFT the MP can be merged now

[shizhMSFT]

@SamirPS The DCO check failed. Could you fix that?

[SamirPS]

yes i will do it

[FeynmanZhou]

Please wait for a while. I tested snap install oras but it looks like Snap gets the ORAS from the main branch. This is not stable. We need to use a specific tag or GitHub release for v1.0.0

 oras version
Version:        1.0.0+unreleased
Go version:     go1.20.4
Git commit:     dd6865a980650e4ff2eca2db771f7772a73e2cb3
Git tree state: dirty

[SamirPS]

@FeynmanZhou now i use the tag and pinpoint the version on the snapcraft.yaml file

samir@samir-Laptop:~/testoras/oras$ oras version
Version:        1.0.0
Go version:     go1.20.4
Git commit:     b58e7b910ca556973d111e9bd734a71baef03db2
Git tree state: clean

[SamirPS]

This snapcraft build snap for amd64,arm64 and s390x