style(button): standardize button styles and replace el-button

[youngbeom-shin]

What this PR does:

style(button): standardize button styles and replace el-button

Which issue(s) this PR fixes:

Fixes #

Type of changes
Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Feature/Issue validation/testing:

Please describe the tests that you ran to verify your changes and relevant result summary.

• Test A

• Test B

• Logs

Special notes for your reviewer:

Checklist:

• I have added unit/e2e tests that prove your fix is effective or that this feature works.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• I have reviewed my own code and ensured that it follows the project's style guidelines.

Release note:

MR Summary:

The summary is added by @codegpt.

This Merge Request focuses on standardizing button styles across the application by replacing the el-button component with a new standardized button class. Key updates include:

1. Updated button classes in InviteMember.vue, NewOrganization.vue, OrganizationDetail.vue, and OrganizationEdit.vue to use new standardized styles.
2. Removed specific size and color classes in favor of more generic btn, btn-primary, and btn-secondary-gray classes.
3. Adjusted button layouts and spacing to accommodate new styles, ensuring a consistent look and feel across different components.

[starship-github]

MR Evaluation:

This feature is still under test, evaluation are given by AI and might be inaccurate.

After evaluation, the code changes in the Merge Request get score: 79-83.

Analysis for the evaluation score:

• The code change may not include corresponding unit tests.
• The code change may not include corresponding integration testing.
• The code change may not include the corresponding user manual.
• The code change may not include the corresponding development documentation.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

Note: Be mindful of the bot's finite context window.
It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.
For a focused discussion, use review comments to chat about specific files and their changes, instead of using the MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.

About Us:

Visit the OpenCSG StarShip website for the Dashboard and detailed information on CodeReview, CodeGen, and other StarShip modules.

[zhendi]

LGTM